W3C home > Mailing lists > Public > www-talk@w3.org > March to April 2000

HTTP proxy implementations

From: Joris Dobbelsteen <j.p.tdobbelsteen@freeler.nl>
Date: Thu, 16 Mar 2000 17:37:35 +0100
To: <www-talk@w3.org>
Message-ID: <000701bf8f65$ef5aaff0$260435d5@Thuis.local>
www-talk mailing list @ w3.org

I had a project for a proxy server. The proxy is subjected to use HTTP/1.1
as a base for it's File and Streaming protocols that are supported (e.g.
HTTP, FTP, Gopher, optional mms (microsoft media server), e.d.). This means
the implementation should be protocol independ, without losing support for
caching e.d. Maybe even other protocols can be accessed using the HTTP/1.1
proxy server, but so far I leave it by these protocols, but implementations
with POP3, SMTP and IMAP should be easy to make.

The questing was how to use HTTP/1.1 as a protocol-independ 'platform' and
how to coordinate the transactions between different protocols.

I supposed to divide the proxy into a couple of services that all do there
own things:
          - Core:  sets up and coordinates the connection between different
services.
          - Incoming:  accept client connections and translate them
          - Outgoing:  makes a connection to the internet server or to the
upstream proxy server
          - Storage:  caches, mailboxes, e.d.

I was not sure how to make a implementation for all these protocols, however
I figured I might need something for different protocols: mail-based
section, routing-based section, e.d. inside the proxy server.




                       - Joris Dobbelsteen......

(Please put replies on top of the mail, keeps them in order of time)
Received on Thursday, 16 March 2000 11:36:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:24 GMT