|
Re: Why MD5 Headers are Imperative: msg#00414network.syndication.atom.protocol
> >Well, I think everything will be much simpler if they are. It seems to >me that you're trying to optimize for a use case that doesn't need >optimization. > But the APP is not at liberty (is it) to change the underlying Atom Format specification. It is a fundamental flaw when a publishing protocol breaks, or is at odds with, the underlying specification of the documents it is meant to manipulate. The APP should not conveniently ignore this discrepancy by calling efforts to work within RFC 4287 "optimizations". -EJB |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: PaceNoServiceDocument: 00414, Eric J. Bowman |
|---|---|
| Next by Date: | Re: Why MD5 Headers are Imperative: 00414, Eric J. Bowman |
| Previous by Thread: | Re: Why MD5 Headers are Imperativei: 00414, Eric Scheid |
| Next by Thread: | Re: Why MD5 Headers are Imperative: 00414, Julian Reschke |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |