PageBox architecture is designed to distribute presentation processing on a large number
of machines hosting a PageBox agent whose our implementation is named JSPservlet.
There can be private set of PageBox used in Intranet or Extranet.
There can also be public - Internet - PageBox sets we call constellations.
Ursa project aims to create such constellations on existing ASPs infrastructure.
- Presentations run in Java 2 sandboxes with permissions granted by policy files.
To be granted extra privileges they must be signed with a certificate delivered by a valid authority.
These features are supported by the current JSPservlet/publisher implementation and do not require
- Presentation deployment uses HTTP over SSL.
This feature is also supported by current implementation.
- Presentation publishing uses HTTP over SSL and allows identifying both the publisher
(content provider) and the editor. This feature has to be developed.
PageBox infrastructure relies on the use of certificates. CRL and Certificate Authority
certificate can be checked on an LDAP server.
- Redirection and load balancing
JSPservlet supports HTML static files as resources.
The redirection relies on the ability of JSPservlet to parse these pages and change their
HREF to point on other URLs.
- Load balancing
JSPservlet uses round-robbin algorithm and a standard feature of Publisher.
Publisher can be queried in HTTP for the list of subscribers for a given archive.
A redirection on JSPservlets based on geographical criteria (where the user is querying from?)
has to be implemented. It relies on DNS analysis and on whois.
If the DNS name ends with a country code such as fr or kr, then the request is routed on
JSPservlets installed in the same state.
If the DNS name ends with com, net... then JSPservlet uses whois.
- Central servers invocation
PageBox architecture includes the creation of VPN between PageBoxes and central systems
to carry client/server requests.
This mechanism is however incompatible with the non-intrusive approach of Ursa constellations.
Therefore we recommend to use protocols relying on SMTP or HTTP for communication with central servers.
SOAP is appropriate.
You can also use RMI and CORBA protocols over HTTP.
These protocols are proprietary but can provide better performance.
Please contact firstname.lastname@example.org if you want
to know more or to participate to that initiative.
©2001-2004 Alexis Grandemange