Seems reasonable to me...A design approach I would have taken. One question. Is there some sort of versioning built into the protocol? One verb yes, but the dictionary numbers the definitions.....
On Mon, Mar 31, 2014 at 12:35 PM, Melanie <mela...@t-data.com> wrote: > This isn't designed as RPC, it's designed as REST. One URL/VERB > combination for each function. > We wanted to get away from the RPC concept. Let's not take backwards > steps here. > > Melanie > > On 31/03/2014 15:15, Oren Hurvitz wrote: > > This isn't overloading: it's an RPC endpoint that accepts many methods. > You > > wouldn't create a separate endpoint for each method, would you? > > > > > > > > > > -- > > View this message in context: > http://opensim-dev.2196679.n2.nabble.com/Optimize-pushing-assets-to-other-grids-tp7579093p7579104.html > > Sent from the opensim-dev mailing list archive at Nabble.com. > > > > > > > > _______________________________________________ > > Opensim-dev mailing list > > Opensim-dev@lists.berlios.de > > https://lists.berlios.de/mailman/listinfo/opensim-dev > _______________________________________________ > Opensim-dev mailing list > Opensim-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/opensim-dev > -- No essence. No permanence. No perfection. Only action.
_______________________________________________ Opensim-dev mailing list Opensim-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/opensim-dev
