|
From: Artyom B. <ar...@z2...> - 2003-03-21 13:34:04
|
On Wed, Mar 19, 2003 at 03:51:55PM +0100, Simon de Bakker wrote: > Another thing to think about is how clients will receive the main name-server IOR. > > Most simple way is the person setting up the name-server mails it to people > that need it. But this makes 'spontanious' jamming very difficult. So a > central name-server might be an option. Is not very urgent now but good > to keep in mind. well, i was thinking about that and thought that many different solutions are possible and should be implemented. that's why i wanted the libv2jam to be separated and contain nice API hiding all disgusting CORBA guts. mailing is alright option, but i'm afraid every time you restart a nameserver ior changes. i thought the following can be a decent system: scrip that runs local name server puts its ior in a well known place (say /var/run/name-server.ior). then every instance of simca has it. then there should be a module in the first simca that you run which will listen for connections on certain port and answer simple requests there. ior of the name server will be one of the requests. this way you just type "simca://nerve.v2.nl:5000/server1/foo/bar" in your client and it will send request for ior name to something listenning to port 5000 on nerve and then use that name server to resolve server1/foo/bar part. BTW, i'm glad you've started to code with me again, even though we have a bit of a clash at the moment :) i'll resolve it in a couple of minutes. -- Artem Baguinski: <ar...@v2...> <http://www.artm.org/> V2_lab: <http://lab.v2.nl/> <http://www.v2.nl/> |