--- Peter Golde <[EMAIL PROTECTED]> wrote:
> Isn't SOAP such an effort?

;-)

The downside is that even though there has been talk about the independence of
the transport, wsdl and particularly uddi have a very web centric view.  While
soap is in thoery more transport agnostic, pretty much all the tools are built
around a tcp/web model.  What would really be great would be a uddi-like tool
not centered around things like business entities but instead on bringing a
browser of java apis into a .net tool and visa versa. More like CORBA/IDL I
suppose. The wsdl would be used to produce the "intellisense" in vs.net and
code generators would build the connection.  Then, there could/would need to be
some alternative to tcp to invoke soap to actually make the calls, like shared
memory, jni, something really fast.

I have been watching the tools and hoping that something like this could be
possible but at this point it looks like a pretty large development effort.

__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

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

Reply via email to