Allow a metaserver to proxy another metaserver's listing

Registered by Sean Ryan

This would allow you to startup a metaserver in "proxy" mode. What this would do is to connect to another metaserver, and periodically do a listreq on it, and populate it's own data structure based on that.

This has 2 main benefits:
1) Non-production testing. With this, you can simulate having lots of connected ( and real working servers ) to a development metaserver.
2) Scalability. In the situation where there are too many clients/servers for the support of a single metaserver, the query load could be shared, in a load balanced situation.

This would require the following configuration options:

metaserver.proxy.mode="OFF|master|slave"
   OFF - current implemenation
   master - Serve as a normal metaserver ... maintain data store, session timeouts, etc.
   slave - would service all read requests, relay write requests to the master, and periodically slave the data from the master.
metaserver.proxy.master=metaserver.worldforge.org ( the master metaserver )
metaserver.proxy.interval=10s ( the time between pulls ).

The intent is to mimic a stealth dns setup where you have a master and some proxy/workhorse servers to take the load.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.