Not at all. Just don't want people to be surprised when they don't see it
in OPAM.

An Irmin backend should be simple and straightforward. Could use session
ids for branch ids and then each one could have its own history. Maybe?

Anyways, all that's necessary is to implement the following signature, and
put the implementation into backends/irmin:


https://github.com/inhabitedtype/ocaml-session/blob/master/lib/s.mli#L53-L95

-Spiros E.

On Wed, Dec 16, 2015 at 2:30 PM, Anil Madhavapeddy <[email protected]> wrote:

> Woops, hope I didn't jump the gun!  I'm so excited that these components
> are forming around CoHTTP, and are also Mirage-friendly.
>
> -anil
>
> On 16 Dec 2015, at 19:26, Spiros Eliopoulos <[email protected]> wrote:
>
> Thanks, Anil!
>
> I haven't officially cut the 0.1.0 release but will shortly. Gotta
> proofread stuff.
>
> Any feedback you have, let me know!
>
> -Spiros E.
>
> On Wed, Dec 16, 2015 at 2:08 PM, Anil Madhavapeddy <[email protected]>
> wrote:
>
>> I didn't release this, but I'm pointing it out on behalf of Spiros!
>>
>> https://github.com/inhabitedtype/ocaml-session
>>
>> > ocaml-session is an session manager that handles cookie headers and
>> backend storage for HTTP servers. The library supports CoHTTP and
>> Webmachine; Async and Lwt; and pluggable backing stores based on a functor
>> interface.
>> >
>>
>> With an Irmin backend, should be awesome for cookie storage (a good
>> pioneer project, Spiros?)
>>
>> -a
>>
>>
>>
>> _______________________________________________
>> MirageOS-devel mailing list
>> [email protected]
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>>
>
>
>
_______________________________________________
MirageOS-devel mailing list
[email protected]
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

Reply via email to