caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Spiros Eliopoulos <seliopou@gmail.com>
To: "Török Edwin" <edwin+ml-ocaml@etorok.net>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: ocaml-session
Date: Fri, 18 Dec 2015 11:36:45 -0500	[thread overview]
Message-ID: <CAEkQQg+5Ud_BXQWzr+PzAgPt5eP1E+yDXLawMsBRc9EhP_YygQ@mail.gmail.com> (raw)
In-Reply-To: <56742C6F.4060905@etorok.net>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

On Fri, Dec 18, 2015 at 10:55 AM, Török Edwin <edwin+ml-ocaml@etorok.net>
wrote:

> >
> > The library ships with an in-memory backend (for development and
> testing) and a postgresql-ocaml[0] based backend.
>
> How about signed cookies as a storage backend?
> Python Flask and Django can use it to store session entirely in the
> cookies with an hmac signature and expiration time, so your server can be
> entirely stateless.
> As long as the amount of data in your session is small, and all you need
> is authenticated data (and not secret data) I think its quite an elegant
> solution,
> and more fitting with a functional style.
>

This is interesting. As far as I can tell, it should be possible to
implement this as a backend without any modifications to module signatures.

Now of course comes the question Cryptokit or nocrypto :)


That decision, for better or worse, has already been made by ocaml-session:
it uses nocrypto to generate session keys.

-Spiros E.

[-- Attachment #2: Type: text/html, Size: 1852 bytes --]

  reply	other threads:[~2015-12-18 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 18:51 Spiros Eliopoulos
2015-12-18  8:53 ` François Bobot
2015-12-18 15:55 ` Török Edwin
2015-12-18 16:36   ` Spiros Eliopoulos [this message]
2015-12-18 16:52   ` Bruno Deferrari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEkQQg+5Ud_BXQWzr+PzAgPt5eP1E+yDXLawMsBRc9EhP_YygQ@mail.gmail.com \
    --to=seliopou@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=edwin+ml-ocaml@etorok.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).