[mapguide-internals] RESTful Ramblings of a Restless Lunatic
Robert Bray
rbray at robertbray.net
Thu Oct 11 12:13:03 EDT 2007
Jason,
I just did some checking and the way I read the URI specification (RFC
3986) square brackets [ ] are not valid within the path portion of a
URI. Hence they would need to be encoded as %5B and %5D.
Someone else should probably look and validate that. I decided to check
because I have never seen brackets used within a URI path before, and
non-standard syntax always raises a flag in my head.
Bob
Robert Bray wrote:
> I have no objection to the bracket approach for parameters. The main
> aspect of my proposal was around using the resources as RESTful
> resources and supporting alternate representations. If you buy this
> approach feel free to simply hack the alternate parameter spec approach
> along side the existing ones in the same WIKI page. That way it will be
> easier to compare/contrast the two styles. If the whole resource model
> is different then a different page would be more appropriate.
>
> Feel free to fix those PUT and POSTs while you are at it :)
>
> Bob
>
> Jason Birch wrote:
>> The more I think about this stuff, the more I'm leaning towards Haris'
>> initial practice of using [] to indicate filters/parameters applied at
>> each level of the resource. I believe that the benefits of this
>> notation outweigh the fact that it doesn't look like a filesystem. For
>> instance, your feature can look like either /feature[2352] or
>> /feature[zone=%22RS-1%22] or
>> /feature[http%3A%2F%2Fmgserver%2Fmgrest%2Fsession%5B215tge54356%5D%2Ffil
>> ter%5B32654%5D] (which is pointing at
>> http://mgserver/mgrest/session[215tge54356]/filter[32654]). I haven't
>> had time to do this yet, but I think that it would be worthwhile to set
>> up a parallel wiki page that shows how this implementation would work.
>>
>> As an aside, it appears that there are quite a few areas of the current
>> wiki that are still using PUT instead of POST where relevant.
>>
>> Jason
>>
>> -----Original Message-----
>> From: Robert Bray
>> Subject: Re: [mapguide-internals] RESTful Ramblings of a Restless
>> Lunatic
>>
>> Actually it is possible to have multiple selections per runtime map.
>> Only one can be rendered at a time at the moment, but you can have
>> multiple. They are currently defined to be a seperate session bound
>> resource type.
>> _______________________________________________
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
More information about the mapguide-internals
mailing list