[omniORB] Small tweak for local object detection

Tue Sep 3 15:28:00 2002

--------------000301060604070502050006
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

HI,

>>So, any better ideas how to achieve the hot-standby functionality? The
>>basic requirement is that host A be able to vanish (as in the hardware
>>just suddenly goes *POOF!* and is no longer there) and that requests (on
>>persistent objects) be redirected to host B transparently to any client
>>(in particular, clients should not have to get new object references).
>>    
>>
>
>You can publish the addresses of all the replicas in all the IORs,
>
How we do this on server side? How can I publish an IOR having address 
of both Server A and Server b? In my case Server B is a hot-standy for 
Server-A. So when server A goes down, client should start using 
reference of Server B.

> and
>rely on the clients to do the fail-over. That assumes that the clients
>know how to do that. omniORB 4 clients do.
>  
>
Should the 'Fall-over ' be taken care by client..or the client's ORB?
In our case client might be on a different ORB, so is there a way to 
make them implement this 'fall-over'?

Thanks in advance,
KV Rao.

--------------000301060604070502050006
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
HI,<br>
<br>
<br>
<blockquote type="cite"
 cite="mid200209031353.g83Dr1803142@pc1-cmbg2-4-cust148.cam.cable.ntl.com">
  <blockquote type="cite">
    <pre wrap="">So, any better ideas how to achieve the hot-standby functionality? The
basic requirement is that host A be able to vanish (as in the hardware
just suddenly goes *POOF!* and is no longer there) and that requests (on
persistent objects) be redirected to host B transparently to any client
(in particular, clients should not have to get new object references).
    </pre>
  </blockquote>
  <pre wrap=""><!---->
You can publish the addresses of all the replicas in all the IORs,</pre>
</blockquote>
How we do this on server side? How can I publish an IOR having address of
both Server A and Server b? In my case Server B is a hot-standy for Server-A.
So when server A goes down, client should start using reference of Server
B.<br>
<br>
<blockquote type="cite"
 cite="mid200209031353.g83Dr1803142@pc1-cmbg2-4-cust148.cam.cable.ntl.com">
  <pre wrap=""> and
rely on the clients to do the fail-over. That assumes that the clients
know how to do that. omniORB 4 clients do.
  </pre>
</blockquote>
Should the 'Fall-over ' be taken care by client..or the client's ORB? <br>
In our case client might be on a different ORB, so is there a way to make
them implement this 'fall-over'?<br>
<br>
Thanks in advance,<br>
KV Rao.<br>
<br>
</body>
</html>

--------------000301060604070502050006--