It's a trade-off. I wouldn't suggest using SOAP based web services over the
public Internet if you have some other solution that meets your
requirements. However, web services solve a specific problem that is
currently unsolvable otherwise:
1. Interoperability between platforms/languages. (Debatable at present)
2. Firewall friendly Internet RPC.
If these are requirements of your situation than you don't have much choice
outside of web services--without rolling your own binary protocol
implementation for performance. If you need RPC, but don't require the
interop or internet then check out some other RPC technology, such as RMI,
CORBA, DCOM.
As for the request broker/UDDI thing, I don't have a clue what your talking
about.
- Ryan
-----Original Message-----
From: P Sreenivasa Rao [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 7:22 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: performance issues in Web Services
Hi all,
I have some doubts regarding the performance issues(u can call them as
disadvntages ) of Web Services.
Actually,we'll depend on the performnace of Service Provider in web
services.So in the internet scenario,the performance will be a bottleneck as
it'll take much time (due to more no of hops or more traffic to SP etc) to
get response.
Another thing, I dont know the necessity of request broker in the web
serives scenario.Is it replaced by UDDI registry or UDDI registry is the
implementation of request broker?Is there any public UDDI registry
available? I tried with IBM's site but I dint get the actaul link pointed in
their documentation.
Finally,what are the other advantages and bottlenecks in this Web serivces
scenario.
Thanks a lot for one and all.
Awaiting your early response.
Thanks and regards,
Sreenivas,CMCLtd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
