[Prev][Next][Index][Thread]
cl-http cohabitation & port 80
Maybe this is ignorant, but perhaps someone can help me better
understand
the relationship of cl-http to port 80 and to other server "demons".
Does cl-http need to "own" port 80, or is there some flexible way it
could be
useful over other ports?
The issue is that a lot of potential clients are already committed to
running
some other primary Web server for some random external reason, so while
cl-http might offer a lot of value, there's no way it can displace
whatever's
currently serving www.foo.com.
Would cl-http have to run on a different host, and get linked to from
the "home"
host, or are there other cohabitation models?
The recent note about "uploading" links that can be used to establish
non-WWW
internet "sessions" (perhaps on other ports or even sockets?) sounded
intriguing
and relevant to our application; is it?
Apologies for the confused questions, but any clarification would
(obviously)
be helpful. Thanks!