Web service client, with embedded web server for SOAP callbacks - need clear guidance

From: Paul McGuire (ptmcg_at_austin.rr._bogus_.com)
Date: 01/04/05 

Date: Tue, 04 Jan 2005 04:53:04 GMT

I am working on an industrial application that reports data from industrial
processes. I am working to an industry standard interface spec, so I cannot
refactor the partitioning or redesign the interfaces. Here is my problem.

The industrial process implements a web service for registering data
collection schemes. I have to develop a client to receive the data.
To receive the data, the client code:
1. defines a data collection plan (creates local object, using types defined
in WSDL)
2. downloads the data collection plan to the process equipment (synchronous
method call)
3. activates the data collection plan, passing a URL for a callback
(synchronous method call)
4. listens for and collects data reported to the URL over SOAP (asynchronous
callback to client)
5. later deactivates the data collection plan

So the client must also implement a web service server to handle the
callback data reports.

I can't run the callback using IIS, so I plan to run an embedded web server
using Cassini-like technology. I can run the wsdl utility against the
consumer interface WSDL file, to generate the abstract proxy stub and data
types, and I can implement the derived class to actually perform the work.
But how do I tie the implementation object that instantiates the data
consumer class to the generated Host, Connection, and RequestHandler/Worker
classes? The incoming "request" (actually a data report) comes in over
SOAP, so I need something that will listen HTTP, render SOAP XML into method
invocation and deserialize method parameters, run my implementation, and
then reserialize any return parameters and send the response back over
SOAP/HTTP.

Can't use SOAP SDK 3.0, sproxy chokes on the complex data types defined in
the spec's WSDL.

Would prefer to use C# and .NET Framework 1.1. I read about HTTPListener in
the ServiceStation article, but this is in .NET Fwk 2.0, which is still
beta, and not sure I will be able to use it in my client environment.

I have googled far and wide for "web services", "without IIS", "eventing",
"remoting", you-name-it. I could really use some expert pointers. I'm lost
amid the come-and-go jargon, and can't figure out which technology horses
are today's stallions but tomorrow's goats.

Thanks!
-- Paul

Relevant Pages

  • no doubt Lenerss striped tear
    ... revival may divert more jails. ... tender node is the client that reports especially. ...
    (sci.crypt)
  • Re: Tech question - interface between receiver and central station software
    ... > years in the computer industry. ... putting the patrol and monitoring ... > information together in the Client table was dumb, ...
    (alt.security.alarms)
  • Architecture question
    ... Fairly complex, PCU-intensive reports acessed monthly ... DB server and the network, but the super-expensive reports I think are ... too much to ask a central server and the company's network. ... required on the client machines to generate them (rather than a saved ...
    (microsoft.public.dotnet.general)
  • Re: Client inventory encryption
    ... I will worry about the "unable to verify client ......". ... >> out that report to my secondary site are reporting in correctly....I am ... >>> If the reports are being rejected, it could be that the MP for the ... >>> I think your problem is not encryption but DDR processing. ...
    (microsoft.public.sms.inventory)
  • Re: fileevent saying theres something to read but there isnt ?!
    ... fileevent callback requires? ... the upstream client -- you tell the client that data can be read ... This polling is stateless in the ... event stream reports the changes to the master so that they can be ...
    (comp.lang.tcl)
Quantcast