The formatting is not hewn in stone. I prefer positional /field1/field2/field3 over name/value ?param1=field1&parem2=field2¶m3=field3, mainly because the fields we do agree on should not be optional. Parameter format provides for optional data, but I believe all data we decide to include should be mandatory, as optional data makes the code to complex to maintain easily.
Melanie Ai Austin wrote: >>From: [email protected] >>protocol://authority/resource_type/resource_id[/cacheable_data] > > +1 > > consider ensuring that at least the name is provided in a form that > can be resolved fast and locally by including the avatar > firstname+lastname - in whatever form the providing grid wishes to > address issues raised by others - so long as the strings are "legal" > in the creator/owner fields. > > would it be worth making sure that the "cachable data" is in the form > of keyword=value pairs, and hence put in a "parameter" form after ? > rather than a final /? > > protocol://authority/resource_type/resource_id[?key_value_pair[,...]] > > with a minimum suggested (or > required?) avatarname=firstname+lastname if the resource_type = user > > > > > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev > > _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
