Hi all,

Fine with me. It definitely makes transactions clearer and simpler. Another 
advantage is that in case or errors at the client or server side, the 
consequences are limited  to a smaller set of requested objects.
Sabine


De : [email protected] [mailto:[email protected]] De la part de Richard 
Alimi
Envoyé : mardi 14 mai 2013 18:25
À : [email protected]
Objet : [alto] Number of media types per resource

When we started specifying the format of the Information Resource Directory 
(IRD), one concern was the overall size.  As such, we designed mechanisms to 
allowed a single entry in the IRD to specify that it could handle multiple 
media types (both in the request  and could provide multiple media types).  
Based on some recent (off-list) discussions with Wendy, this may be less of a 
concern and we may want to go for simplicity.

Here's an example of one entry we have now:


       {

         "uri" : "http://custom.alto.example.com/maps";,

         "media-types" : [

           "application/alto-networkmap+json",

           "application/alto-costmap+json"

         ],

         "accepts" : [

           "application/alto-networkmapfilter+json",

           "application/alto-costmapfilter+json"

         ]

       }

The proposal is to have each entry declare exactly one media-type for the 
response, and either 0 or 1 media types for the request (e.g., the unfiltered 
cost map doesn't need anything in the request - it's a simple GET).

Here's what the corresponding entry from above would look like:






       {

         "uri" : "http://custom.alto.example.com/maps";,

         "media-type" : "application/alto-networkmap+json",

         "accepts" : "application/alto-networkmapfilter+json",

       },  {

         "uri" : "http://custom.alto.example.com/maps";,

         "media-types" : "application/alto-costmap+json",

         "accepts" : "application/alto-costmapfilter+json",

       }





The editors think this is a reasonable change to make.  Comments are very 
welcome.




Since we are on a tight schedule here, if we don't hear anything within the 
next week (by May 21st), we will make the corresponding changes to the draft.

Thanks!
Rich



_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to