[mapguide-internals] RESTful Ramblings of a Restless Lunatic

[Jason Birch]

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.