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

Re: [MirageOS-devel] [Cohttp] Proxy and Client information

Hi Romain,

Sorry I don't really understand your first point. Probably because I know little of ocsigen's functionality.

Your second question I can possibly answer however. It's true that this information seems to suppressed in the Lwt backend (not in the async backend as far as I can tell). But instead of creating a server isn't it easier to just change Connection.t to include that information? The type is abstract so you wouldn't break anybody.



On Fri, 11 Apr 2014 09:24:12 -0400, <romain.calascibetta@xxxxxxxxx> wrote:


I am Romain Calascibetta and I work on the integration of the Cohttp Library in the Ocsigen Server Project. For now, I try to take control with this Library and understand as you do.

After much research, I have some questions ð !

The first question concerns the management of pipeline and proxy server. I noticed that you are managing the pipeline as HTTP server but Ocsigen integrates an extension of reverse proxy request reordering queries. For this problem, I thought connecting pipeline managementâs proxy server Ocsigen over Cohttp. It just enough for me to know if it is managed or not.

The second question concerns the client information. I understand the callback system with as an argument, the client ID, the request and body. But Ocsigen requests information such as the IP address and port of the client (or more precisely its sockaddr) and I wondered if there would be a way to get them. I think it would create another module Server with another interface (I could do to better understand the project and propose pull-request).

Thand you for your answers.


Romain Calascibetta - http://din.osau.re/

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.