[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "cooperative" services (was Re: [DotGNU]Last call for 'This Year ...

From: Ian Fung
Subject: Re: "cooperative" services (was Re: [DotGNU]Last call for 'This Year ...')
Date: Wed, 1 Jan 2003 15:42:24 -0500

right. so there is a demuxer for connections, ie it uses one port say for the Jabber transport, but multiple webservices can use that one transport. so is there anything special about this type of cooperation verses a "normal" scheme where each webservice uses its own port and communication between webservices on the same machine would take place over the loopback? (if the answer is no, then that's good. otherwise, please explain)

"Normal" network services make themselves available by attaching to a
port on the system and listening for all connections to that port.
The distinction I make is that webservices share the network transport
(be it port or Jabber connection) rely on an external coordinator
(see*port, in this case) to understand a common protocol (HTTP on port
80, e.g.) and extract a "path" in order to figure out which service
should receive the request.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]