Well, strictly speaking TCP is not a stream. There is stuff that
happens to make data over TCP appear to be a stream. I think you would
prefer to write code using sockets rather than TCP per se. And for
anything that is just a stream, one would still need a defined format
for how things get streamed.
> 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.
There are many ports that are available to the average Jane for
whatever she wants. Are we going to assign a specific protocol to
every port in the land? Just so we can take the protocol label out of
the URL?
> 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...
I don't see why one could not do that. But I think we would need a
better URL than "tcp:port//blah".
-Patrick
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.
