On 1/28/06, Sam Ruby <[EMAIL PROTECTED]> wrote: > > James M Snell wrote: > > > > This pace requires that a server either accept > > everything that is given to it or declare exactly what it will accept up > > front. > > If this pace is scheduled, I will -1 it. > > The APP needs to take a "Small Pieces, Loosely Joined" approach. > > A server may reject entries that contain pub:slugs that are 32,768 bytes > long, or contain text that is critical to the Chinese government, or > contain entirely well-formed and valid entries that are encoded in EBCDIC. > > And yet, very few of us would ever be affected by any such restrictions. > > Similarly, very few of us would be affected by a site that prohibit > markup in titles.
That depends, what do you mean by prohibit? That there is silent data loss, i.e. the server strips markup from titles? Or do you mean that the server sends a 4xx response with an error report that the server does not accept entries with markup? In this case you are shifting the problem from the client developer's shoulders onto the client users' shoulers. -joe -- Joe Gregorio http://bitworking.org
