> You can talk directly to my http-based services, or you can talk
> directly to my xmpp-based services, or anything else I provide. They
> may actually be the same services on the backside if all I have is a
> driver for http and a driver for xmpp, and those drivers go to the
> same services. You could bypass the http and xmpp drivers if I
> provided some other driver. But it would still be a driver, and you
> would still have to know *how* to talk to it.
It is just a stream of data. We let HTTP ride on TCP to provide an application
protocol. Everyone assumes that if you connect to port 80, you get an HTTP
application, not an RMI endpoint for example. So, if you know enough about the
port you are connecting to, you can just call it a TCP port. Different ports in
the IANA database document the application protocols associated with the ports
so prescribed. I'm just wondering why application protocols can't be
implemented in _javascript_. Imagine the possibilities if _javascript_ could do RPC
to an RMI or CORBA endpoint...
Gregg Wonderly
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
