Re: [Vrs-development] VRS and SEE/DEE goals

[Chris Smith]

On Monday 25 March 2002 10:34, Tim Terlegård wrote:

> <thinking_loud>
> Thinking peer-2-peer. A Virtual Remote Server could be a peer. An ASP could
> be a VRS. All users that want to use the ASP is a part of a larger VRS
> (that includes the ASP VRS) and think they contact a single ASP server,
> when they matter a fact communicates with a cluster. Every VRS node runs a
> lookup service, which enables anyone to browse the web services available
> on any node or browse the complete VRS. A VRS node can also turn this off.

You're going along the same thinking as me :o)
This is exactly what I was referring to when I suggested that any LDS in a 
VRS cluster may open themselves up as 'public access' nodes.  Clients think 
they are accessing a single server, but are infact accessing a cluster.
Any 'public' LDS allows access to the cluster.  
BUT we need a Service Discovery Server of some sort that can advertise the
services available in the VRS.

I would modify your 'thinking' slightly and say that:
"Every VRS node runs a lookup service, which enables anyone to browse the web 
services available on the complete VRS.  Because there may be multiple LDS's 
acting as public entry points to the VRS cluster, each LDS must advertise the 
same services in their lookup service."

Any service deployed within the VRS may be tagged as 'private'.  These 
servicdes will NOT be advertised to the outside world by public facing LDS's.

> This allows a VRS cluster to have a single server as a lookup directory
> (although this makes it less p2p, the webservices can still be requested in
> a pure p2p manner.).

Hmm.  Multiple lookup servers would be good.
This is kind of extended DNS isn't it.

Cheers
Chris

-- 
Chris Smith
  Technical Architect - netFluid Technology Limited.
  "Internet Technologies, Distributed Systems and Tuxedo Consultancy"
  E: address@hidden  W: http://www.nfluid.co.uk