Jon Smirl wrote:
Any suggestions on the best way to rework nsHttpChannel to support server oriented connections? A server version of nsHttpChannel can reuse most of the existing protocol code it just needs to flip the transaction around from send/receive to receive/send.
Hm... I'm not sure that this is going to work so well... all that code assumes it's working as a client. That means that it always starts with a URL, connects to a server, parses the response, stores it in cache, and delivers the data to a listener.
I would think that using http channel for a server would require rewriting much of it; I doubt you can reuse much, maybe some of the header parsing, maybe the connection manager.
Feel free to prove me wrong though :-) -biesi
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
