W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1995

Re: Draft Minutes of HTTP Working Group, 33rd IETF Meeting, Stockholm

From: Bill Janssen <janssen@parc.xerox.com>
Date: Tue, 8 Aug 1995 13:54:39 PDT
Message-Id: <sk9wwD0B0KGWM98yRS@holmes.parc.xerox.com>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Excerpts from ext.ietf-http: 31-Jul-95 Draft Minutes of HTTP Worki.. Jim
Gettys@w3.org (4887*)

> Who has implemented a non-blocking (streaming) RPC system that can
> be used if we are to avoid rolling our own?

I've sent mail to Jim on this separately, but I wanted to point out that
ILU, which is freely available in source form for both commercial and
non-commercial use, includes an implementation of a non-blocking RPC
system.  ILU provides support for both synchronous (blocking) or
asynchronous (non-blocking) calls.  Since ILU is protocol-independent,
many different on-the-wire protocols can be used with it.  Two different
on-the-wire protocol implementations are provided with the ILU sources,
the ONC RPC wire protocol and the XNS Courier wire protocol.  It would
be easy to implement another wire protocol for ILU embodying HTTP, but
it seems more useful to use a more efficient binary protocol.  All wire
protocols used with ILU share the semantics and infrastructure provided
by ILU, including its careful management of resources such as file
descriptors, connections and buffers.  User-level code is never aware of
the specific wire protocol being used.

More ILU info is at ftp://ftp.parc.xerox.com/pub/ilu/ilu.html.

Received on Tuesday, 8 August 1995 13:56:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:14 UTC