You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Eric VERGNAUD <er...@jlynx.com> on 2006/05/19 01:31:44 UTC

Re: soap for inter-process communication

I think you may find what you need in RMI which was designed  
precisely for this task.

Eric

Le 4 avr. 06 à 23:26, Chris Rocker a écrit :

> Hello,
> I'm considering using SOAP / HTTP for inter-process communication.  
> The reason is that the related processes could be located either on  
> the same computer, or on separate hosts depending on the situation.  
> In my experience, processing SOAP messages requires a separate  
> server, which seems like overkill for IPC. However, using SOAP/HTTP  
> (instead XML and plain sockets) seems to provide some  
> standardization benefits, although I'm not completely clear on how.  
> I guess because the applications will all have been configured to  
> interact with a SOAP server.
> In my experience, using SOAP has required a separate application  
> server. I'd like to build this logic (eg., process the the HTTP,  
> parse the soap envelope) as a separate component of our application  
> instead of using an app server with all the footprint, setup and  
> overhead considerations.
>
> I'd be grateful for some guidance in this area.
>
> Cheers,
> Chris
>
>
> Blab-away for as little as 1¢/min. Make PC-to-Phone Calls using  
> Yahoo! Messenger with Voice.


Apache SOAP 2.3.1 and Java

Posted by Martin Cavanagh <ma...@yahoo.com.au>.
Does anyone have any experience running Apache SOAP 2.3.1 and Java 1.5/1.6?

Currently I'm using Java 1.4 but I would like to update to 1.5/1.6, but 
I've noticed that under Java 1.5 on some Clients my SOAP calls sometimes 
slow down to a factor of 100-1000 times slower - does anyone have any 
experience with this problem?  Any tips?  I am unable to reliably 
reproduce this problem - it could be client configuration setting that 
I've missed, but it always only surfacing under Java 1.5+ (even on dual 
Java installations)

Basically I want a smooth transition path for my Java Web Start 
application - involving either first changing for a new Java 
Installation and then later using its newer built in SOAP/Web Service 
support or changing my SOAP implementation to a new external library, so 
which supports Java 1.4 and 1.5/1.6.

Does anyone have any ideas?

Thanks

Martin Cavanagh
Send instant messages to your online friends http://au.messenger.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@ws.apache.org
For additional commands, e-mail: soap-user-help@ws.apache.org