[OSM-dev] 0.5 API: /api/0.5/user/preferences, values truncated to 256 chars

[Shaun McDonald]

On 25 Nov 2008, at 16:46, Tom Hughes wrote:

> Shaun McDonald wrote:
>
>> On 25 Nov 2008, at 16:39, Tom Hughes wrote:
>>> Indeed - in fact can anybody give an example of when the update_all
>>> method would be useful, given that it drops all existing prefs? In  
>>> fact
>>> if that is exposed via a route then I would say we should remove it
>>> immediately as it is clearly exceedingly dangerous.
>> I remember Steve saying this was something to do with the REST  
>> mantra.
>
> I don't see how - allowing GET/PUT/DELETE on individual preferences,  
> plus a POST to create new preferences, would be exactly RESTish.
>

Maybe he was thinking of all the preferences as a whole document.....

What we could do is to make it update the preferences that are sent,  
rather than deleting all the preferences. This would be done as a  
POST. Also being able to fetch all preferences that start with a  
particular key may prove useful for things like editors getting all  
their prefs.

Shaun


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2433 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20081125/45d3d607/attachment.bin>