but still, does it means all our remoteadmin tools are worhtless ?
On Fri, Feb 20, 2009 at 8:08 AM, John Sheridan <[email protected]>
wrote:
<< sighs >> And here's to messy old Firefox borking a copy/paste! :P
John Sheridan wrote:
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
<http://en.wikipedia.org/wiki/Object-oriented_programming>
<http://en.wikipedia.org/wiki/Object-oriented_programming> (termed
/remotable object/) available across /remoting boundaries/, which
includes different appdomains <http://en.wikipedia.org/wiki/Appdomain>
<http://en.wikipedia.org/wiki/Appdomain>,
processes <http://en.wikipedia.org/wiki/Process_%28computing%29>
<http://en.wikipedia.org/wiki/Process_%28computing%29> or even
different computers connected by a network.^[4]
<http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3>
<http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3> The
.NET Remoting runtime hosts the listener for requests to the object in
the appdomain <http://en.wikipedia.org/wiki/Appdomain>
<http://en.wikipedia.org/wiki/Appdomain> 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
<http://en.wikipedia.org/wiki/Transmission_Control_Protocol>
<http://en.wikipedia.org/wiki/Transmission_Control_Protocol> streams,
HTTP <http://en.wikipedia.org/wiki/HTTP>
<http://en.wikipedia.org/wiki/HTTP> streams and named pipes
<http://en.wikipedia.org/wiki/Named_pipe>
<http://en.wikipedia.org/wiki/Named_pipe>. 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
<http://en.wikipedia.org/wiki/Serialization>
<http://en.wikipedia.org/wiki/Serialization> and marshalling
<http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29>
<http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29> of
objects across the client and server appdomains.^[4]
<http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3>
<http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3> "
(http://en.wikipedia.org/wiki/.NET_Remoting)
- Orion Pseudo
Sacha Magne wrote:
Hmm, what means "remoting" in english for us, mortal users ?
thanks
Sacha
On 2/20/09, Frisby, Adam <[email protected]> <[email protected]>
wrote:
+1
> -----Original Message-----
> From: [email protected] [mailto:opensim-users
<opensim-users>-
> [email protected]] On Behalf Of Diva Canto
> Sent: Thursday, 19 February 2009 8:57 PM
> To: [email protected]
> 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
> [email protected]
> https://lists.berlios.de/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing
