<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>That sounds like an elegant and correct solution; provided, of course that the only callers are also in the clientstack.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Mon, 18 Aug 2008 20:03:09 +0900<BR>> From: mmazur@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Upcoming work on alternative client stack<BR>> <BR>> Hi,<BR>> <BR>> On Mon, Aug 18, 2008 at 7:28 PM, Stefan Andersson <stefan@tribalmedia.se> wrote:<BR>> > * First of all, can the whole InPacket() construct in client manager be<BR>> > refactored so that the specific type knowledge moves into the client<BR>> > stack?<BR>> <BR>> This is something Johan pointed out to me a little while ago. In<BR>> ClientManager.cs, the InPacket(circuitcode, packet) method takes the<BR>> circuit code, looks up the client that matches the circuit code, then<BR>> passes the Packet to the client's InPacket() method.<BR>> <BR>> Instead, what it should probably do is return the client.<BR>> <BR>> Johan's pseudo code:<BR>> - ClientManager.InPacket(circuitcode, packet);<BR>> + ClientManager.FindClient(circuitcode).InPacket(packet);<BR>> <BR>> After all, the ClientManager, strictly speaking, should deal with the<BR>> clients, not their packets.<BR>> <BR>> > * Passing objects around and recasting them is generally an indication<BR>> > of needing to re-think things.<BR>> <BR>> That sounds right. I don't think the answer to "How do we do this?"<BR>> should be "You don't."<BR>> <BR>> Thanks for the feedback!<BR>> Mike<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>