Re: when to use SOAP

The usage would be average with some spikes and we want to use ssl.  Both
boxes will be Sun running Solaris with Apache web servers and as I mentioned
before both client and server pieces will be written in perl.  For the
specific application that we are looking at now, the application on box 2
will accept requests only from box 1.  Other web services which live on box
2 (which already use SOAP) may accept requests from other clients.

Again, thank you for your help.

-----Original Message-----
From: Bruno Georges [mailto:[email protected]]
Sent: Friday, August 02, 2002 9:00 AM
To: [email protected]
Subject: Re: [SOAP] when to use SOAP


Diane

Can you also tell us a bit more details, for exmaple about the usage
pattern, how frequently calls are made, etc...
I am thinking about performance, if your infrastructure can't support
the overhead of SOAP, you probably need to investigate other solutions
such as traditional RPC calls over TCP/IP.
Think about scalability also. Maybe SOAP over http between box1 and box2
is not the best option.
Also are box1 and box2 [boxn,.. if any] are sing the same OS?

Correct me if I am wrong but it looks like you want to expose some of
the services on box2 to the web via box1.
Box1 acts as a proxy and connects to box2 over http. Box1 is accessed
via http from a browser but isn't exposing SOAP services to the outside
world.

webbrowser <----- http ----> box1 <------- SOAP/http ----> box2 [service]

If this is correct, one of the benefit of using SOAP between box1 and
box2 is that you can simulate a  DMZ, restricting access to box2.
Box2 interface to Box1 listen for HTTP only.

You will have to add some rules to Box1 and Box2 and also shutdown the
non required services on your boxes.

webbrowser <----- http ----> box1 [http only /port 80/443] <-------
SOAP/http ----> box2 [service, http on interface to box1 ] <-----> you

Hope this helps

Bruno

Keddie, Diane wrote:

>We have recently begun using SOAP to create web services with perl and are
>considering using it again for a new application which requires server to
>server communication.  Since the new application is not actually going to
be
>a web service which will be accessed from multiple clients,  I am wondering
>if it is the best option.
>
>Given the choice between using SOAP to have a client script on box 1 call a
>routine on box 2 OR to have box 1 act as a proxy server and just pass on a
>request to box 2 what would be the best option and why.  The only reason we
>are using two boxes is so that the services on box 2 are not directly
>accessible from a browser.  The application is not intended to be a web
>service called by multiple clients.
>
>My knowledge of both SOAP and proxy is limited, so I appreciate any input
>from more experienced sources.
>
>-Diane
>
>You can read messages from the SOAP archive, unsubscribe from SOAP, or
subscribe to other
>DevelopMentor lists at http://discuss.develop.com.
>
>

You can read messages from the SOAP archive, unsubscribe from SOAP, or
subscribe to other
DevelopMentor lists at http://discuss.develop.com.

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.