Re: panel error *** ORBit patch ***



On Thu, Aug 13, 1998 at 04:35:01 PM -0400, Elliot Lee wrote:
> Simple example:
> Person runs GNOME desktop sessions on hosts A and B. All is well.
> 
> Both panels have a UNIX socket path of /tmp/username/GNOME-panel, but
> since they are on two different hosts, there is no namespace clash.
Hmm?  Why?  Shouldn't that be /tmp/username/IOR:<ior_of_panel_on_A>, and
/tmp/username/IOR:<ior_of_panel_on_b>, where ior_of_panel_on_A !=
ior_of_panel_on_B, and another file /tmp/username/orbit?  The two would have
different IORs, so there is REALLY no namespace clash.

> Person wants to run a "super stock ticker" applet on host B, but have it
> displayed in their panel on host A.
So, the sst process, which is on host B, checks if ORBit is already running.
It sees /tmp/username/orbit, and knows that it is.  It asks for the IOR of
panel on A, and ORBit (it is an object request broker, after all) notices
that it isn't host A, and finds host A and gets the IOR?  That dosn't
require any persistincy of IPs... mearly the ORBit on B trying to send a
packet to itself using the given hostname (or IP) of B, and not reciving it
(and not getting a ENOSUP or such).  If you get the packet back, then host A
== host B.  If you don't, then host A and B are distinct.  If you had
network problems, then you should have gotten an error, and not a packet
that simply went off into the void.

OK, so tell me why I'm crazy.

	-=- James Mastros
-- 
A basement-GNOME (http://www.gnome.org/) with PIP (IETF group) and WINE
(http://www.winehq.com/).  Not really as impressive as it might sound, or as
Tolkinen.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]