|
Re: Why MD5 Headers are Imperative: msg#00473network.syndication.atom.protocol
> >Sure. I did not hear anyone saying that they thought the problem was >as bad as you thought, and others have said they don't understand >what you are saying. Until there is strong agreement that there is a >serious problem, we should not consider a solution such as that would >be difficult to implement. "Change HTTP" seems pretty darn difficult. > The other alternative is "Change RFC 4287" as I see it. I still am unsure how this would be expressed in a Pace -- "PaceAllowPrincipleOfOrthogonality", perhaps? There is no direct, one-to-one relationship between a resource and a representation, and a protocol which flies against this cannot possibly meet any 80/20 reasonableness standard. -EJB |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Why MD5 Headers are Imperative: 00473, Eric J. Bowman |
|---|---|
| Next by Date: | Re: Why MD5 Headers are Imperative: 00473, Joe Gregorio |
| Previous by Thread: | Re: Why MD5 Headers are Imperativei: 00473, Joe Gregorio |
| Next by Thread: | Re: Why MD5 Headers are Imperative: 00473, Eric J. Bowman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |