Backing up a bit, I think we need to start with the fact that a grid provides a common start point for an avatar logon. By that, I mean, a grid will have some quantity of users in the users MySQL or MSSQL table with a particular avatar appearance and some semblance of an inventory.
For the purpose of HyperGrid, many folks wish to travel from grid->grid, standalone->grid, standalone->standalone or grid->standalone. And most of those folks will expect to have their avatar appearance constant based on their original logon place as they HG around. So, from the most basic point, we can say that our current and most reasonable use case is an avatar with custom edits and some inventory that logs onto a particular standalone or grid and then expects to be able to HyperGrid to a different grid and have that avatar and inventory stay reasonably constant. That is, the avatar should not be ruthed. In order to accomplish this in the general case is a bit tricky and I believe is one of the issues being worked on currently. A number of other things begin falling out of this notion after this one is working reliability and consistently such as the other things brought up in this thread. But, I think it all begins with a desire for a consistent avatar and inventory experience while HyperGridding. Charles
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
