rgrinberg is right. If you want a good web framework built on cohttp that is NOT as challenging as ocsigen/eliom then I'd definitely point you to opium.
NOT using cohttp/lwt/core/batteries fills a niche on its own - i.e. owebl is very lightweight.
There is also currently no major reason (read: production users or interest) for me to stop using owebl as an educational tool to grok HTTP, concurrent/distributed computing, etc.
NOT using cohttp/lwt/core/batteries fills a niche on its own - i.e. owebl is very lightweight.
There is also currently no major reason (read: production users or interest) for me to stop using owebl as an educational tool to grok HTTP, concurrent/distributed computing, etc.