On Thursday, July 11, 2013 8:47:26 AM UTC-4, Klaus Aehlig wrote: > > > > +The following resources will be added. > > > + > > > +- /2/filters/ > > > + - GET returns the list of all currently set filters > > > + - POST adds a new filter > > > + > > > +- /2/filters/[uuid] > > > + - GET returns the description of the specified filter > > > + - DELETE removes the specified > > > > > > The "Format of a Filter Rule" section suggests that one can provide a > UUID > > at filter creation time. If that's true, there should be a POST method > on > > this resource. > > Not a PUT? In any case, I wasn't thinking about this, as it could be > expressed > by a POST to /2/filters with the uuid specified in the filter rule > description. > > But you're right. Let's keep the interface systematic and add PUT here as > well. >
Yes, PUT is the more appropriate method here. Thanks, Tim > > -- > Klaus Aehlig > Google Germany GmbH, Dienerstr. 12, 80331 Muenchen > Registergericht und -nummer: Hamburg, HRB 86891 > Sitz der Gesellschaft: Hamburg > Geschaeftsfuehrer: Graham Law, Katherine Stephens >
