From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 9B7DB7ED1D for ; Wed, 14 Oct 2015 22:55:35 +0200 (CEST) IronPort-PHdr: 9a23:iU069B3YrzPOqUOmsmDT+DRfVm0co7zxezQtwd8ZsegTKvad9pjvdHbS+e9qxAeQG96Lt7QU1KGP7vqocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWM5DIfUi/yKRBybrysXNWC04LniKvrpsebSj4LrQT+SIs6FA+xowTVu5teqqpZAYF19CH0pGBVcf9d32JiKAHbtR/94sCt4MwrqHwI6Lpyv/JHBILRdqE8BehTBTEidmQ0/9HDtB/ZTALJ6GFKAUsMlR8dOBDE9hbhFrr1syzisfd53zLSadb7SbEzQTO/x6huQR7sziwAMmhqoynslsVsgfcD81qarBtlztuMbQ== Authentication-Results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=seliopou@gmail.com; spf=Pass smtp.mailfrom=seliopou@gmail.com; spf=None smtp.helo=postmaster@mail-lb0-f175.google.com Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of seliopou@gmail.com) identity=pra; client-ip=209.85.217.175; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="seliopou@gmail.com"; x-sender="seliopou@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of seliopou@gmail.com designates 209.85.217.175 as permitted sender) identity=mailfrom; client-ip=209.85.217.175; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="seliopou@gmail.com"; x-sender="seliopou@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-lb0-f175.google.com) identity=helo; client-ip=209.85.217.175; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="seliopou@gmail.com"; x-sender="postmaster@mail-lb0-f175.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CLAQAswB5Wm6/ZVdFeg3puBrEPjXMhgnKCCn+BRwc8EAEBAQEBAQEBEAEBAQEBBgsLCSEugh+CIBEdARseAxIJAQY3AiQBEQEFASI1h3YBAxINoBmCCIExPjGLSYFsgnmIfwoZJw1WhCkBCxoBAQQOhmiJQEeCdIFFBZYVhRmIAo5Zi2USI4EXOIIvI4F3IjOGbwEBAQ X-IPAS-Result: A0CLAQAswB5Wm6/ZVdFeg3puBrEPjXMhgnKCCn+BRwc8EAEBAQEBAQEBEAEBAQEBBgsLCSEugh+CIBEdARseAxIJAQY3AiQBEQEFASI1h3YBAxINoBmCCIExPjGLSYFsgnmIfwoZJw1WhCkBCxoBAQQOhmiJQEeCdIFFBZYVhRmIAo5Zi2USI4EXOIIvI4F3IjOGbwEBAQ X-IronPort-AV: E=Sophos;i="5.17,682,1437429600"; d="scan'208";a="182824142" Received: from mail-lb0-f175.google.com ([209.85.217.175]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 14 Oct 2015 22:55:34 +0200 Received: by lbwr8 with SMTP id r8so55151528lbw.2 for ; Wed, 14 Oct 2015 13:55:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=HkgSyCNmwGbE2OQ128/tRbugzAFLwfqGgnbC4yH1QfI=; b=jqEJ6YwpdLZuKTA8Zi+FkCLfLIeLSt3SE2FOH4ogrnXnG+gjA+gJka5rEiTTKbE/9o nbnaFVz5/ITDSVYOCb+aXAOxw35oyowlb/jhkHL+ceVslOqPzfci9OTnNH4HBzvsCUxT jyGuqL1eidOV/jXOVMJRRpTBfj3R7mmm6267pvKuPk2oyOgs9ZXLurkQyOpkNJAsodx9 z07gWXrlp7kc4KEbol8+RQsJPT1w50JxF3GhUKMgAi9BfcdU4e8GfDldr7yLgT325DZf f4xOlGZxWFdjgbTOsZb3EQaluqvtLbVJcCk1SjmHjbY4VYjuWBl1GruZOPLqIII+CeCW hdwg== X-Received: by 10.112.17.105 with SMTP id n9mr2763908lbd.78.1444856134244; Wed, 14 Oct 2015 13:55:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.213.2 with HTTP; Wed, 14 Oct 2015 13:55:14 -0700 (PDT) From: Spiros Eliopoulos Date: Wed, 14 Oct 2015 16:55:14 -0400 Message-ID: To: OCaml Content-Type: multipart/alternative; boundary=001a11c3bfeea21e1c052216c838 Subject: [Caml-list] ANN: ocaml-dispatch --001a11c3bfeea21e1c052216c838 Content-Type: text/plain; charset=UTF-8 Hey List, I'm happy to announce the initial release of ocaml-dispatch: https://github.com/inhabitedtype/ocaml-dispatch ocaml-dispatch provides a basic mechanism for dispatching a request to a handler based on hierarchical path names conventionally found in URIs. It can be used both for dispatching requests in a server, as well as handing changes to hierarchical fragments in a client-side application via js_of_ocaml. The code for this package originated from the webmachine[0] project. The dispatch package is now a dependency of webmachine as of the 0.2.0 release. You can find dispatch.0.1.0 in OPAM currently, and webmachine.0.2.0 there shortly. There are some small projects in the issue tracker if anybody would like to contribute. Issues and pull requests welcomed. -Spiros E. [0]: https://github.com/inhabitedtype/ocaml-webmachine --001a11c3bfeea21e1c052216c838 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey List,

I'm happy to announce the= initial release of ocaml-dispatch:

=C2=A0 =C2=A0<= a href=3D"https://github.com/inhabitedtype/ocaml-dispatch" target=3D"_blank= ">https://github.com/inhabitedtype/ocaml-dispatch

<= div>ocaml-dispatch provides a basic mechanism for dispatching a request to = a handler based on hierarchical path names conventionally found in URIs. It= can be used both for dispatching requests in a server, as well as handing = changes to hierarchical fragments in a client-side application via js_of_oc= aml.

The code for this package originated from= the webmachine[0] project. The dispatch package is now a dependency of web= machine as of the 0.2.0 release. You can find dispatch.0.1.0 in OPAM curren= tly, and webmachine.0.2.0 there shortly.

There are= some small projects in the issue tracker if anybody would like to contribu= te. Issues and pull requests welcomed.

-Spiro= s E.

--001a11c3bfeea21e1c052216c838--