Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Spiros Eliopoulos <seliopou@gmail.com>
To: OCaml <caml-list@inria.fr>
Subject: [Caml-list] ANN: dispatch 0.2.0 with js_of_ocaml support
Date: Thu, 22 Oct 2015 01:39:48 -0400	[thread overview]
Message-ID: <CAEkQQgKyPvoyogL-7d6V9TN+_7VuC8AX-xBAM6RaTBsqZ2nO-w@mail.gmail.com> (raw)

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

Hey List,

I'm happy to announce the latest release of dispatch. What's notable about
this release is that it includes out-of-the-box js_of_ocaml support.
Specifically, it allows you to easily set up front-end applications to use
the URI fragment to track state transitions and history. For example:

let fragment_thread =
  Dispatch_js.dispatch_on_fragment ~default:"/" [
      ("/"         , root_handler)
  ; ("/user/:id/", user_handler)
  ]

... creates a thread that will monitor for URI fragment changes and
dispatch to the appropriate handler. In addition, it will set the initial
fragment to "/" and ensure that the handler for that path is initially
called; even if the fragment was already set to "/" when the thread
started, dispatch will still occur.

Due to the API changes included in this release, webmachine[0]'s version
has been bumped to 0.2.1. You can find both the new version of dispatch and
webmachine on OPAM.

Full but short release notes can be found here:

  https://github.com/inhabitedtype/ocaml-dispatch/releases/tag/0.2.0

As always, issues and pull requests welcomed.

-Spiros E.

[0]: https://github.com/inhabitedtype/ocaml-webmachine

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

                 reply	other threads:[~2015-10-22  5:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAEkQQgKyPvoyogL-7d6V9TN+_7VuC8AX-xBAM6RaTBsqZ2nO-w@mail.gmail.com \
    --to=seliopou@gmail.com \
    --cc=caml-list@inria.fr \
    /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