Go Back   ZeroC Forums > Help Center

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old 03-07-2005
mario mario is offline
Registered User
 
 
Join Date: Dec 2004
Posts: 24
Routing of request

Hello,

I have some machines running in a local network and one, and only one of they, take the role of the active server of the network at a precise moment. This server role is dynamic, all machines can be servers but only one at the same time.

In each on this machines, some client processes must connect to the dynamic server whithout the knowledge of the endpoints of the Object Adapters at the server machine.
The IcePack service can't help here because this configuration is dynamic, it changes at runtime.

I think one solution is a local service running in all machines, that know the exact location of the dynamic server at runtime. This local service can listen at 127.0.0.1 to the request of the client processes and forward this request to the dynamic server and, of course, return the server's response to the corresponding client.

What is your advice with this situation? Maybe something close to the Glacier service?

Thanks and best regards,
Mario.
Reply With Quote
  #2 (permalink)  
Old 03-07-2005
marc's Avatar
marc marc is offline
ZeroC Staff
 
Name: Marc Laukien
Organization: ZeroC, Inc.
Project: The Internet Communications Engine
 
Join Date: Feb 2003
Location: Florida
Posts: 1,781
You could write a router that forwards requests from the clients to the server as blobs. Note that I don't mean a full implementation of the Ice::Router interface (such as Glacier), but simply a process that forwards requests, similar to IceStorm.

Such router could listen to a fixed port on the loopback interface, and forward all requests to a server that is configured by whatever means are appropriate for your application. Your server would then use the loopback address and the chosen port for it's published endpoints, so that if the server returns a proxy to the client as a result of an operation call, such proxy would point to the router instead of to the server directly.

Yet another solution would be to implement the Ice::Locator interface, i.e., to write a custom locator service similar to IcePack. This would be the cleanest solution, but it would be more work than the simple router.
Reply With Quote
  #3 (permalink)  
Old 03-08-2005
mario mario is offline
Registered User
 
 
Join Date: Dec 2004
Posts: 24
Thanks marc

I'm going to read "32.3.2 Dynamic Dispatch using Blobject" of the Ice tutorial following your advice.

Best regards,
Mario.
Reply With Quote
Reply



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
In Process Request. luuma Comments 14 09-25-2006 10:16 PM
Exception routing with Glacier DeepDiver Help Center 2 02-22-2006 10:08 AM
Request for more and better documentation bartley Comments 3 01-26-2006 04:13 PM
load balancing and routing suroot Help Center 1 05-12-2005 06:18 AM
AMI and cancelling the request vsonnathi Help Center 2 04-05-2005 10:43 AM


All times are GMT -4. The time now is 05:00 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.0.0
(c) 2008 ZeroC, Inc.