Sorry, I may have become sidetracked. Passing the clients IP/FQDN:port to the server to allow callback would effectively make the client a web service in itself? To set this up would I need to run the axis servlet (and servlet engine) on the client side as well, or is it possible to run a more minimal system there?
My thought was, could using Jabber solve the direct IP addressing and DNS lookup problems when the client is behind a masqueraded internet connection or firewall? Evan ----- Original Message ----- From: "Jim Dixon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 02, 2002 09:44 Subject: Re: pass by reference in Axis > On Tue, 2 Apr 2002, Evan Jehu wrote: > > > Would it be possible to do something like SOAP over Jabber (the open source > > chat system) this could allow a 2 way 'conversation' between the client and > > server? > > > > If you think that could work? is so any thoughts on how it could be > > implemented? > > The original question had to do with passing a remote reference, which > would be used to enable the server to publish information to a number > of clients. > > In the simplest approach, both parties understand how the information > is going to be structured. In this case, the client just has to tell > the server how to reach it, so the client only has to tell the server > where to send the information. This is most easily specified as > FQDN:port or ipAddress:port. > > If the structure isn't certain, the client could send to the server > FQDN:port plus a WSDL description of the communication. > > Or am I missing something? > > > Evan > > > > > > ----- Original Message ----- > > From: "Jim Dixon" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, April 02, 2002 09:10 > > Subject: Re: pass by reference in Axis > > > > > > > On Tue, 2 Apr 2002, Steve Loughran wrote: > > > > > > > > Is it possible to pass a remote reference using SOAP and Axis? I > > would > > > > like > > > > > to establish a publisher-subscriber style relationship between a > > client > > > > > (which implements a listener interface) and an Axis web service. > > > > > > > > > > I have created the web service class, event class (Serializable) and > > event > > > > > listener interface (modeled on SWING) but WSDL2Java creates a class > > for > > > > the > > > > > listener interface when I really need to pass a reference to the > > client > > > > for > > > > > the service to call when events occur. > > > > > > > > > > Also is it possible to operate in the other direction, could a web > > service > > > > > create a new object which it passes as a remote reference to the > > client > > > > and > > > > > if so how could you do it? > > > > > > > > do you meant that you want to do callbacks from a SOAP service to the > > > > client? > > > > > > > > If that is the case there is no easy solution at all, not one that works > > > > over HTTP and through firewalls and things. You need polling, or > > different > > > > transports like STMP somewhere in the solution. > > > > > > Couldn't he accomplish what he needs to do by passing to the server > > > the fully qualified domain name + the port he would be listening on? > > > > > > -- > > > Jim Dixon [EMAIL PROTECTED] tel +44 117 982 0786 mobile +44 797 373 7881 > > > ---------- THAT'S A CHANGE OF ADDRESS: I'm no longer [EMAIL PROTECTED] -------- > > > > > > > > > > > > -- > Jim Dixon [EMAIL PROTECTED] tel +44 117 982 0786 mobile +44 797 373 7881 > ---------- THAT'S A CHANGE OF ADDRESS: I'm no longer [EMAIL PROTECTED] -------- >
