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

[MirageOS-devel] Cohttp Design -- LWT, Async, JS, Mirage Compatibility

Hi all,

I was wondering if there is a document somewhere describing why the different backends to cohttp don't have a unified client/server interface? It seems like it would be such a boon for the user to be able to write their code but be able to choose the backends. I realize that this must have already received much discussion but am not sure where it is located.


MirageOS-devel mailing list



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