Let's be honest people, software developers and companies loves to
make protocols AND API's "better" by putting in their own additions.
It's been this way to ages and I don't think this is going to change in the
future nor would I like to this to change because this is what drives
developers to create better software.
Most of the discussion around ESB is around protocol, but I'm making
my ESB act as a general purpose protocol and API gateway.
There is an option to create an inter/intra-wide standard and make
every application interface (protocol and API) conform to that standard.
However, I've found that it is much more difficult to get consensus from
all the departments involved and to get it implemented. This doesn't mean
I don't think it's not necessary to have a standard, but just that it is
sometimes
difficult to get a project completed in time. IMHO, technology is sometimes
much more flexible than people. : )
H.Ozawa
jeffrschneider wrote:
> Which is more resilient (stands the test of time):
>
> TCP/IP or WinSock?
>
> Why?
>
> Jeff
>
> Mark - Let's see if Gregg can get this one on his own ;-)
>
>
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
