<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Agreed with Trucker - I'm a bit out of my league in this part but I'm
pretty sure remote admin runs off an XML-RPC type of structure, a
different mechanism from remoting and probably a different section of
the system from what Diva is mentioning?<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:trucker.anthony@3rdrockgrid.com">trucker.anthony@3rdrockgrid.com</a> wrote:
<blockquote cite="mid:1ac25646eb4a8dcc2abd500f09130e74@3rdrockgrid.com"
type="cite">
<pre wrap="">no it has nothing to do with remoteadmin access it is the way in which the
regions communicate with eachother and across multiple servers
TA
On Fri, 20 Feb 2009 08:47:35 +0100, Sacha Magne <a class="moz-txt-link-rfc2396E" href="mailto:sacha.magne@k-grid.com"><sacha.magne@k-grid.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">but still, does it means all our remoteadmin tools are worhtless ?
On Fri, Feb 20, 2009 at 8:08 AM, John Sheridan <a class="moz-txt-link-rfc2396E" href="mailto:john@pseudospace.net"><john@pseudospace.net></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> << 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
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Object-oriented_programming"><http://en.wikipedia.org/wiki/Object-oriented_programming></a>
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Object-oriented_programming"><http://en.wikipedia.org/wiki/Object-oriented_programming></a> (termed
</pre>
<blockquote type="cite">
<pre wrap="">/remotable object/) available across /remoting boundaries/, which
includes different appdomains <a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Appdomain"><http://en.wikipedia.org/wiki/Appdomain></a>
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Appdomain"><http://en.wikipedia.org/wiki/Appdomain></a>,
</pre>
<blockquote type="cite">
<pre wrap="">processes <a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Process_%28computing%29"><http://en.wikipedia.org/wiki/Process_%28computing%29></a>
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Process_%28computing%29"><http://en.wikipedia.org/wiki/Process_%28computing%29></a> or even
</pre>
<blockquote type="cite">
<pre wrap="">different computers connected by a network.^[4]
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3"><http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3></a>
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3"><http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3></a> The
</pre>
<blockquote type="cite">
<pre wrap="">.NET Remoting runtime hosts the listener for requests to the object in
the appdomain <a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Appdomain"><http://en.wikipedia.org/wiki/Appdomain></a>
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Appdomain"><http://en.wikipedia.org/wiki/Appdomain></a> of the server
</pre>
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Transmission_Control_Protocol"><http://en.wikipedia.org/wiki/Transmission_Control_Protocol></a>
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Transmission_Control_Protocol"><http://en.wikipedia.org/wiki/Transmission_Control_Protocol></a> streams,
</pre>
<blockquote type="cite">
<pre wrap="">HTTP <a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/HTTP"><http://en.wikipedia.org/wiki/HTTP></a>
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/HTTP"><http://en.wikipedia.org/wiki/HTTP></a> streams and named pipes
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Named_pipe"><http://en.wikipedia.org/wiki/Named_pipe></a>
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Named_pipe"><http://en.wikipedia.org/wiki/Named_pipe></a>. As a result, by instantiating
</pre>
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Serialization"><http://en.wikipedia.org/wiki/Serialization></a>
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Serialization"><http://en.wikipedia.org/wiki/Serialization></a> and marshalling
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29"><http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29></a>
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29"><http://en.wikipedia.org/wiki/Marshalling_%28computer_science%29></a> of
</pre>
<blockquote type="cite">
<pre wrap="">objects across the client and server appdomains.^[4]
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3"><http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3></a>
<a class="moz-txt-link-rfc2396E" href="http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3"><http://en.wikipedia.org/wiki/.NET_Remoting#cite_note-overview-3></a> "
</pre>
<blockquote type="cite">
<pre wrap="">(<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/.NET_Remoting">http://en.wikipedia.org/wiki/.NET_Remoting</a>)
- Orion Pseudo
Sacha Magne wrote:
Hmm, what means "remoting" in english for us, mortal users ?
thanks
Sacha
On 2/20/09, Frisby, Adam <a class="moz-txt-link-rfc2396E" href="mailto:adam@deepthink.com.au"><adam@deepthink.com.au></a> <a class="moz-txt-link-rfc2396E" href="mailto:adam@deepthink.com.au"><adam@deepthink.com.au></a>
</pre>
</blockquote>
<pre wrap="">wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
+1
> -----Original Message-----
> From: <a class="moz-txt-link-abbreviated" href="mailto:opensim-users-bounces@lists.berlios.de">opensim-users-bounces@lists.berlios.de</a> [<a class="moz-txt-link-freetext" href="mailto:opensim-users">mailto:opensim-users</a>
</pre>
</blockquote>
<pre wrap=""><opensim-users>-
</pre>
<blockquote type="cite">
<pre wrap=""> > <a class="moz-txt-link-abbreviated" href="mailto:bounces@lists.berlios.de">bounces@lists.berlios.de</a>] On Behalf Of Diva Canto
> Sent: Thursday, 19 February 2009 8:57 PM
> To: <a class="moz-txt-link-abbreviated" href="mailto:opensim-users@lists.berlios.de">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
</pre>
</blockquote>
<pre wrap="">sims
</pre>
<blockquote type="cite">
<pre wrap=""> > 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 class="moz-txt-link-abbreviated" href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a>
> <a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
_______________________________________________
Opensim-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
_______________________________________________
Opensim-users mailing
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!----><a class="moz-txt-link-abbreviated" href="mailto:listOpensim-users@lists.berlios.dehttps://lists.berlios.de/mailman/listinfo/opensim-users">listOpensim-users@lists.berlios.dehttps://lists.berlios.de/mailman/listinfo/opensim-users</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
_______________________________________________
Opensim-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Opensim-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
</pre>
</blockquote>
<br>
</body>
</html>