but still, does it means all our remoteadmin tools are worhtless ?<br><br><br><div class="gmail_quote">On Fri, Feb 20, 2009 at 8:08 AM, John Sheridan <span dir="ltr"><<a href="mailto:john@pseudospace.net">john@pseudospace.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
<< sighs >> And here's to messy old Firefox borking a
copy/paste! :P<div><div></div><div class="Wj3C7c"><br>
John Sheridan wrote:
<blockquote type="cite">
<pre>If I'm not mistaken the term "remoting" pertains to a remote procedure
call or a way of communicating between processes spread over a network.
".NET Remoting allows an application to make an object
<a href="http://en.wikipedia.org/wiki/Object-oriented_programming" target="_blank"><http://en.wikipedia.org/wiki/Object-oriented_programming></a> (termed
/remotable object/) available across /remoting boundaries/, which
includes different appdomains <a href="http://en.wikipedia.org/wiki/Appdomain" target="_blank"><http://en.wikipedia.org/wiki/Appdomain></a>,
processes <a href="http://en.wikipedia.org/wiki/Process_%28computing%29" target="_blank"><http://en.wikipedia.org/wiki/Process_%28computing%29></a> or even
different computers connected by a network.^[4]
<a href="http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3" target="_blank"><http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3></a> The
.NET Remoting runtime hosts the listener for requests to the object in
the appdomain <a href="http://en.wikipedia.org/wiki/Appdomain" target="_blank"><http://en.wikipedia.org/wiki/Appdomain></a> of the server
application. At the client end, any requests to the remotable object are
proxied by the .NET Remoting runtime over |Channel| objects, that
encapsulate the actual transport mode, including TCP
<a href="http://en.wikipedia.org/wiki/Transmission_Control_Protocol" target="_blank"><http://en.wikipedia.org/wiki/Transmission_Control_Protocol></a> streams,
HTTP <a href="http://en.wikipedia.org/wiki/HTTP" target="_blank"><http://en.wikipedia.org/wiki/HTTP></a> streams and named pipes
<a href="http://en.wikipedia.org/wiki/Named_pipe" target="_blank"><http://en.wikipedia.org/wiki/Named_pipe></a>. As a result, by instantiating
proper |Channel| objects, a .NET Remoting application can be made to
support different communication protocols without recompiling the
application. The runtime itself manages the act of serialization
<a href="http://en.wikipedia.org/wiki/Serialization" target="_blank"><http://en.wikipedia.org/wiki/Serialization></a> and marshalling
<a href="http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29" target="_blank"><http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29></a> of
objects across the client and server appdomains.^[4]
<a href="http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3" target="_blank"><http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3></a> "
(<a href="http://en.wikipedia.org/wiki/.NET_Remoting" target="_blank">http://en.wikipedia.org/wiki/.NET_Remoting</a>)
- Orion Pseudo
Sacha Magne wrote:
</pre>
<blockquote type="cite">
<pre>Hmm, what means "remoting" in english for us, mortal users ?
thanks
Sacha
On 2/20/09, Frisby, Adam <a href="mailto:adam@deepthink.com.au" target="_blank"><adam@deepthink.com.au></a> wrote:
</pre>
<blockquote type="cite">
<pre>+1
> -----Original Message-----
> From: <a href="mailto:opensim-users-bounces@lists.berlios.de" target="_blank">opensim-users-bounces@lists.berlios.de</a> [<a href="mailto:opensim-users" target="_blank">mailto:opensim-users</a>-
> <a href="mailto:bounces@lists.berlios.de" target="_blank">bounces@lists.berlios.de</a>] On Behalf Of Diva Canto
> Sent: Thursday, 19 February 2009 8:57 PM
> To: <a href="mailto:opensim-users@lists.berlios.de" target="_blank">opensim-users@lists.berlios.de</a>
> Subject: [Opensim-users] r8525: no more remoting
>
> Just a heads-up to let everyone know that r8525 departs from .NET
> Remoting for good.
> Post-r8525 sims no longer listen on remoting ports, they use http
> exclusively. This means that those of you who haven't updated your sims
> in the past month or so won't be able to go to places that are up-to-
> date.
>
> The UCI Hypergrid gateways are up-to-date.
>
> _______________________________________________
> Opensim-users mailing list
> <a href="mailto:Opensim-users@lists.berlios.de" target="_blank">Opensim-users@lists.berlios.de</a>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
_______________________________________________
Opensim-users mailing list
<a href="mailto:Opensim-users@lists.berlios.de" target="_blank">Opensim-users@lists.berlios.de</a>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
</pre>
</blockquote>
<pre>
</pre>
</blockquote>
<pre>_______________________________________________
Opensim-users mailing list
<a href="mailto:Opensim-users@lists.berlios.de" target="_blank">Opensim-users@lists.berlios.de</a>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Opensim-users mailing list<br>
<a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><br><a href="http://K-grid.com">http://K-grid.com</a><br>Just be cause it's Kool<br>