• Post Reply Bookmark Topic Watch Topic
  • New Topic

Corba specification or vendor implementation behavior?

 
Peter Tran
Bartender
Posts: 783
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Scenario: I have two corba servers call them X and Y. I want to start multiple instances of these servers in different process space for load balancing. E.g.
---- ---- ---- ----
|X1| |X2| |X3| |X4|
---- ---- ---- ----
|Y1| |Y2| |Y3| |Y4|
---- ---- ---- ----
If I have a client called C1 in a totally different separate process space, and I make several calls to method in in the X servers, then I can bind across to any of the X1, X2, X3, or X4 corba servers.
Problem: The problem is when X1 tries to make a corba call to a method inside the Y server. When I try to bind the different Y servers, for example from X1, I can only see Y1. Is this behavior in the CORBA specification? Why can't I bind to Y2, Y3, or Y4 from X1?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!