<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div><br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;">I would concur. I can certainly see this idea expediting PDA and cell phone group and IM communication into the Metaverse. This seems like an entirely reasonable additional use case as we evolve.<br><br>Charles<br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Mike Mazur <mmazur@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> opensim-dev@lists.berlios.de<br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, February 24, 2009 4:06:04 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Opensim-dev] On solving Authentication and such<br></font><br>
Hi,<br><br>On Tue, 24 Feb 2009 09:45:27 -0800<br>Diva Canto <<a ymailto="mailto:diva@metaverseink.com" href="mailto:diva@metaverseink.com">diva@metaverseink.com</a>> wrote:<br><br>> I think the proposal is exactly the opposite, at least for the time <br>> being. That is, let's use whatever the LL viewer already has for 3D <br>> rendering, and let's move the non-3D features out onto Web<br>> applications.<br><br>The way I understood the proposal is to separate out the 3D and 2D<br>functionality at all(?) levels.<br><br>This means that the server will provide one client stack implementing<br>one protocol that deals only with 3D information. Avatar movement,<br>scene description, agent updates, prim updates, etc. The viewer speaks<br>this protocol in order to display to the user what is happening in the<br>3D world. This makes it possible to write a client that is only capable<br>of viewing the world and doesn't care about inventory. The
protocol<br>could be, for example, the LLUDP protocol.<br><br>The inherently 2D features, such as chat or inventory, can use another<br>protocol. The server will provide a different client stack that deals<br>only with the 2D feature(s). The viewer also implements this protocol to<br>provide these additional services to the user. This 2D information can<br>then be overlaid over the 3D rendering of the world. This allows to<br>write clients that manipulate this data only, like inventory managers,<br>asset browsers, chat-only clients, etc. The protocol used here could be<br>HTTP.<br><br>This separation of protocols for all the different ways a user<br>interacts with the virtual world sounds like a Good Thing (tm) to me.<br><br>Mike<br>_______________________________________________<br>Opensim-dev mailing list<br><a ymailto="mailto:Opensim-dev@lists.berlios.de" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br><a
href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br></div></div></div></body></html>