<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
+1000!<br>
<br>
Michael Wright wrote:
<blockquote cite="mid:143506.6163.qm@web23006.mail.ird.yahoo.com"
type="cite">Does anyone have any objections to splitting the
IUserService interface, so that the Avatar Appearance and attachments
are in their own interface IAvatarService ?<br>
<br>
I really don't think we should be coupling things like we are. I'm not
saying that these functions have to move off the User Server. Just on
the region side, we move them into their own interface, so that if
someone wants those functions to be on a different server, they can
change the url of the server to be different to the user server with
minor code changes. <br>
<br>
When I think about the various Servers, I generally think of the User
server as holding account infomation. The Grid Server as being the
general manager of the "grid". And the Inventory and Asset servers as
the general datastores. <br>
<br>
So to fit in with my view, the avatar appearance data would fit better
on the Inventory server or even a separate server that was part of the
datastore group. This is so that we could have one central User Server,
but a number of Inventory and Asset servers. Each user's in-world data
could be on a different set of those.<br>
<br>
As I've said before, I really think we should have a system that allows
the various backend functions to be where ever a grid admin thinks is
best. But thats still a dream. <br>
<br>
But we can do a small change that would allow a different url to be set
for the Avatar services, if a application required it.<br>
<br>
So what I'm suggesting is we add a new interface to the
CommunicationsManager, like:<br>
<br>
public Interface IAvatarService<br>
{<br>
AvatarAppearance GetUserAppearance(LLUUID user);<br>
<br>
void UpdateUserAppearance(LLUUID user, AvatarAppearance
appearance);<br>
<br>
void AddAttachment(LLUUID user, LLUUID attach);<br>
<br>
void RemoveAttachment(LLUUID user, LLUUID attach);<br>
<br>
List<LLUUID> GetAttachments(LLUUID user);<br>
}<br>
<br>
The OSGrid implementation could be exactly like it is now, and send the
requests to the user server. I'm not even talking about adding a new
setting to the ini file, but just leaving the code so it uses the
UserServer url.<br>
<br>
So its really a minor change, but does decouple these functions from
the more general user account functions. <br>
<p> </p>
<hr size="1"> Not happy with your email address?
<br>
<a moz-do-not-send="true"
href="http://uk.docs.yahoo.com/ymail/new.html"> Get the one you really
want</a> - millions of new email addresses available now at <a
moz-do-not-send="true" href="http://uk.docs.yahoo.com/ymail/new.html">
Yahoo!</a>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>