It's optional, in my mind. It happens to be an extremely valuable piece
of pre-fetched "suggested" data for the receiving grid, one that avoids
having to bounce on grids being down for an guestimate of 75% of the
time (I can start collecting data from MI Search for the exact
percentage of downtime ...) and generally lag the simulators. I think
the idea is brilliant, quite honestly, and it may very well be much more
widely applicable than OpenSim. Strikes me as the right thing to do in
networked systems where the nodes are down frequently and disappear
altogether frequently too, but still we want references to their data to
persist.
Note, however, that this is not a one-way street. The originating user
agent service *suggests* the receiving grid to use the given data,
instead of calling back. However, there's absolutely nothing that forces
the receiving grid to comply with that suggestion.
In other words, if this were to be written as a spec (hint hint) the
wording related to the cacheable_data part of the path MUST read "SHOULD
use" rather than "MUST use" all over.
Mike Dickson wrote:
If the decision is to go ahead and do cache-able data then I'd agree, do
it as attribute NVP's and make them optional. The originating agennt
service is then free to define the semantics of the attributes it
exposes.
Mike
On Sun, 2010-08-29 at 21:42 +0000, 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
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
