RE: New PEP draft available as ID!

I was just sitting down to read through the 23 or so pages of the PEP
draft when I asked myself "Why?" My original interest in PEP was caused
by my work in DAV where I needed to extend HTTP in all sorts of
interesting ways without breaking anything. In the end however, I
discovered the whole effort was largely for not because PEP only works
if everyone supports it and currently, no one supports it. This would be
the famous chicken and egg problem.

However I did spend some time thinking about what the world would look
like if PEP did exist and the answer is "expensive". Having to send
along a bag with all those options, not to mention writing all the
supporting code, just seems like maximum overkill. The solution we are
using in DAV is to have clients look up a particular attribute to see if
a set of features are supported. Once you have attributes, PEP becomes
largely irrelevant.

I realize that PEP is a lot more powerful than a simple "check the
switch" solution but in all the real world scenarios I am looking at,
such as deploying DAV, I don't seem to need anything more than the
attribute. Has someone else had a different experience?

	Thanks,
		Yaron

> -----Original Message-----
> From:	Henrik Frystyk Nielsen [SMTP:frystyk@w3.org]
> Sent:	Monday, April 28, 1997 8:24 AM
> To:	http-wg@cuckoo.hpl.hp.com
> Subject:	New PEP draft available as ID!
> 
> 
> As a result of the discussions at the Memphis IETF meeting and WWW6, a
> new
> version of the PEP draft has been submitted as an ID. I have attached
> the
> draft to this mail.
> 
> You can also find the draft as an W3C working draft at
> 
> 	http://www.w3.org/pub/WWW/TR/WD-http-pep-970428.html
> 
> Please read and comment!
> 
> Thanks,
> 
> Henrik
>  << File: draft-ietf-http-pep-03.txt >>  << File: ATT46336.txt >>

Received on Wednesday, 30 April 1997 15:20:41 UTC