[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Callout Protocol Core - Kept parameter

To: jfcm <info@xxxxxxxx>
Subject: Re: Callout Protocol Core - Kept parameter
From: Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 27 Jun 2006 07:52:27 -0600
Cc: "OPES WG (E-Mail)" <ietf-openproxy@xxxxxxx>
In-reply-to: <7.0.1.0.2.20060627084856.03fe3a88@xxxxxxxx>
List-archive: <http://www.imc.org/ietf-openproxy/mail-archive/>
List-id: <ietf-openproxy.imc.org>
List-unsubscribe: <mailto:ietf-openproxy-request@imc.org?body=unsubscribe>
References: <75F7E67FC45F6744A7D328D41E35376D597FB8@xxxxxxxxxxxxxxxxxx> <444E4F26.7000601@xxxxxxxx> <1151382634.13547.12.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <7.0.1.0.2.20060627084856.03fe3a88@xxxxxxxx>
Sender: owner-ietf-openproxy@xxxxxxxxxxxx

On Tue, 2006-06-27 at 08:49 +0200, jfcm wrote:
> At 06:30 27/06/2006, Alex Rousskov wrote:
> >This is not the only bug in the OCP RFCs. I should publish the
> >errata.
> 
> Did you develop some running code ?

Not me personally, but others have been working on OCP implementations
and discovering bugs in the specs. As far as I can tell, these were all
experimental, short-term projects. Martin Stecher had running code as
well.

Alex.

Follow-Ups:
- Re: Callout Protocol Core - Kept parameter
  - From: jfcm

References:
- Re: Callout Protocol Core - Kept parameter
  - From: Martin Thelian
- Re: Callout Protocol Core - Kept parameter
  - From: Alex Rousskov
- Re: Callout Protocol Core - Kept parameter
  - From: jfcm

Prev by Date: Re: Callout Protocol Core - Kept parameter
Next by Date: Re: Callout Protocol Core - Kept parameter
Previous by thread: Re: Callout Protocol Core - Kept parameter
Next by thread: Re: Callout Protocol Core - Kept parameter
Index(es):
- Date
- Thread