Thanks for your notes, Steve I am going to work through the firewall, so your comments are reasonable - that is, I can't ping the client-side from the server.
How does dotNet with its unsolicited events do that? AFAIK, when building a webservice with C#, a lightweight http server is built in the client-side app to be notified of events. Is it a particular solution for working behind the firewall only? Have you heard about that? Another possibility is to establish a permanent (lasting) connection from the client to the server which will follow some custom notification protocol. On the server side there could be a servlet that never closes the connection and writes small pieces of data to the output stream when new events should be read by the client from the soap endpoint. What would you say about that? Alexey. > -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 09, 2002 8:32 PM > To: [EMAIL PROTECTED] > Subject: Re: events in Webservices > > > > are you all behind the firewall? you cant do http callbacks > through a firewall (which is why it isnt in the spec). If you > are behind the 'wall you could callback by having the app > listen on a socket for an incoming ping that tells it to > 'poll the server now'... > > ----- Original Message ----- > From: "Alexey Krivitsky" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, December 09, 2002 04:25 > Subject: RE: events in Webservices > > > Thanks Alex. > > Approach of polling the webserver cannot be applied here, > because events must be processed as quick as possible. > > Axis on the client's side cannot be deployed, > requirements say no servlet-runners on the client-side. > > So ksoap or something like that can be applied here I hope. > I will try to find links on ksoap to investigate it. > > Thanks > > > >
