caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: james woodyatt <jhw@wetware.com>
To: "Sylvain LE GALL" <sylvain.le-gall@polytechnique.org>
Cc: The Trade <caml-list@inria.fr>
Subject: Re: [Caml-list] ANNOUNCE: pagoda core foundation cf-0.0
Date: Thu, 1 Jan 2004 17:00:48 -0800	[thread overview]
Message-ID: <1A8C6CBE-3CBF-11D8-8FF0-000393B8133A@wetware.com> (raw)
In-Reply-To: <20040101232448.GA1951@grand>

On 01 Jan 2004, at 15:24, Sylvain LE GALL wrote:
>
> Does this library replace IOX ? ( i have made a little package of it 
> for
> debian and i don't have yet released... maybe i could directly use this
> library rather than IOX )

It does not 'replace' Iox, but the fact is I haven't worked on 
improving Iox in quite some time.  I didn't like the semantics of the 
Iox library after I started trying to build complicated components with 
it.

So I went back to the drawing board, and looked at more things that 
others have done-- particularly in the area of using functional 
programming techniques for interactive applications.  I carefully 
studied Thomas Hallgren's and Magnus Carlsson's Ph.D. thesis on the 
Fudget system in Haskell.  (See 
<http://www.cs.chalmers.se/~hallgren/Thesis/> for details.)  I've been 
experimenting around that for several months now, and I'm pretty sure I 
like my new approach over the old one.

I quickly discovered, however, that I needed a core foundation of 
miscellaneous code that didn't really belong in the I/O component 
framework itself.  That core foundation is what you now see in this 
release.  (I decided I needed to get some code published before it 
started to grow mold on it and die.)

In addition to the core foundation, I am currently working on several 
other libraries that are all part of my Pagoda project:

- Iom	a replacement for Iox built with Cf_gadget and Cf_socket.
- Mime	parsing/emitting MIME entities and content-transfer encodings
- Xml	yet another wrapper around Expat, plus some glue for Cf parsers
- Beep	a general implementation of RFC 3080 and RFC 3081 using Iom

These are all in various states of unreleasable incompleteness.  
Though, the Iom, Mime and Xml libraries are fairly close (they just 
need reference documentation).

I also plan to write a DNS resolver for Iom.  I hope to support 
Multicast DNS with it too, i.e. Rendezvous.  I also want to write a 
RADIUS client, and I will need a good wrapper around OpenSSL if I'm 
going to implement the required TLS profile for RFC 3081.  Eventually, 
I'd like to have a nice implementation of RFC 3341, 3342 and 3343 using 
Iom.

> What is pagoda project ?

It's a project I fart around with in my limited spare time, mostly for 
research purposes.  The Iox library came from research early in my 
Pagoda project.  I called it "Pagoda" because that was where I started 
stacking up all my bits and bobs of componentry that I hope will be 
useful in building distributed network service applications.  In 
actuality, it appears to be a dark, mysterious tower filled with shiny 
bits of seemingly useless artifacts whose guardians regard as sacred 
relics.  A pagoda.


-- 
j h woodyatt <jhw@wetware.com>
markets are only free to the people who own them.

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2004-01-02  1:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01 21:10 james woodyatt
2004-01-01 23:24 ` Sylvain LE GALL
2004-01-02  1:00   ` james woodyatt [this message]

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=1A8C6CBE-3CBF-11D8-8FF0-000393B8133A@wetware.com \
    --to=jhw@wetware.com \
    --cc=caml-list@inria.fr \
    --cc=sylvain.le-gall@polytechnique.org \
    /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).