Re: Webservice Callbacks
From: Jan Tielens (jan_at_no.spam.please.leadit.be)
Date: 03/09/04
- Next message: Mark Redman: "Re: Webservice Callbacks"
- Previous message: Mark Redman: "Re: Webservice Callbacks"
- In reply to: Mark Redman: "Re: Webservice Callbacks"
- Next in thread: Mark Redman: "Re: Webservice Callbacks"
- Reply: Mark Redman: "Re: Webservice Callbacks"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Mar 2004 11:18:57 +0100
In that case: yes. But this only works if your clients expose a web service.
This is rather unusual if they are just normal windows applications because
you'll need IIS on each client...
Maybe you could consider a polling mechanism: each client checks each minute
if there are new events waiting.
-- Greetz, Jan ________________________ Read my weblog: http://weblogs.asp.net/jan "Mark Redman" <RedmanSoftware@hotmail.com> schreef in bericht news:uHFsZibBEHA.576@TK2MSFTNGP11.phx.gbl... > Hi Jan, > > Thanks for the reply and info, I think this may work for some calls and will > look into it, but some things may happen where the calling app doesnt call a > function and expect a response but where something happens within the API > and needs to tell the calling application. In this case I still think I need > to write the receiving webservice first? > > Mark Redman > > > "Jan Tielens" <jan@no.spam.please.leadit.be> wrote in message > news:Ofb1PAaBEHA.1796@TK2MSFTNGP12.phx.gbl... > > You could also use async. web services: > > http://tinyurl.com/2r6vg > > Asynchronous Web Service Calls over HTTP with the .NET Framework > > Summary: Matt Powell walks through the various options provided by the > > Microsoft .NET Framework for making asynchronous Web service calls over > > HTTP, which allow for efficient calls to Web services without blocking > > applications while potentially lengthy network calls complete. (11 printed > > pages) > > > > > > -- > > Greetz, > > Jan > > ________________________ > > Read my weblog: http://weblogs.asp.net/jan > > > > "Mark Redman" <RedmanSoftware@hotmail.com> schreef in bericht > > news:ekk48OSBEHA.3064@tk2msftngp13.phx.gbl... > > > Hi All, > > > > > > I have a system with its own API that other systems will integrate with, > I > > > have a webservice with functions etc, no problems there, but some tasks > > will > > > take some time to be done, a function will be called on the webservice > and > > > the tasks will be queued. When the task is done, I would like to have a > > > callback, that will call a webservice on the other system. What is the > > best > > > way to implement this? The "Other" system may be written by a third > party > > > and not necessarily done in .NET etc. > > > > > > Should I just write the Receiving/Listener webservice and create the > WSDL > > > from that, then any other system needs to comform to that? It seems > > > backwards but the only way I can think of doing it? > > > > > > Thanks > > > > > > Mark Redman > > > > > > > > > > > >
- Next message: Mark Redman: "Re: Webservice Callbacks"
- Previous message: Mark Redman: "Re: Webservice Callbacks"
- In reply to: Mark Redman: "Re: Webservice Callbacks"
- Next in thread: Mark Redman: "Re: Webservice Callbacks"
- Reply: Mark Redman: "Re: Webservice Callbacks"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|