Re: Handling unknown elements in an entry

[Dare Obasanjo <kpako@xxxxxxxxx>]

--- Robert Sayre <mint@xxxxxxxxxxxxxxx> wrote:
> 
> I wouldn't expect that. What about the set of
> elements defined by the 
> Atom format? How about adding name/value pairs?[0]
> If clients press 
> their luck, you can always return an error.

It doesn't matter, I don't plan to store arbitrary
data I'm not doing anything with. Server space isn't
free. If we don't support the user specifying the date
for an entry, I don't expect us to store the
'suggested' date sent by the user so we can return it
in the RSS or Atom feed. 


> 
> My view is not set in stone. I'm just looking for a
> way to make this a 
> little easier on clients. If the server's response
> is 100% dependent on 
> its internal data model, that's not much of a
> protocol, is it?


HTTP works exactly this way. I can send If-None-Match
or If-Modified-Since and if the server doesn't support
them they are ignored. It seems you are suggesting
that HTTP servers are either supposed to (a) error or
(b) store these header values and return them even
though they do nothing with them. 

I just can't think of any reason why this is a good
idea. 

THINGS TO DO IF I BECOME AN EVIL OVERLORD #222
I reserve the right to execute any henchmen who appear to be a little too intelligent, powerful, or devious. However if I do so, I will not at some subsequent point shout "Why am I surrounded by these incompetent fools?!"


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250