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

Re: [MirageOS-devel] porting ocsigenserver



On 30 Dec 2013, at 19:28, hugo <hugo.heuzard@xxxxxxxxx> wrote:

> I would like to experiment with mirage and try to port ocsigen/eliom project.
> Are there any ongoing work in that direction ?
> Any advice ?
> What's the status of (native) dynlink ?

Hi Hugo,

Porting Ocsigen and Eliom would be great, but it does require rethinking
how you handle configuration.  In Mirage, all the major dependencies are
functorized across the module signatures in:

   https://github.com/mirage/mirage-types

The V1 module contains the 1.0 versions, and Thomas' pull request shows
the improved ones in V2.  At build time, the `mirage` command line tool
parses a configuration file to determine the concrete module implementations
to satisfy a job.

So to start porting Ocsigen and Eliom, it would be best to understand
how to break it up and interface with these libraries.  Would it be
difficult to swap out the HTTP handler in Ocsigen with Cohttp and run
that under Unix?  Eliom might be slightly problematic due to a clash
between type_conv and deriving-ocsigen.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


 


Rackspace

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