PageBox |
|
| FAQ What is a PageBox?
JSPservlet is a PageBox implementation that relies on existing Java application servers and embedded servers. It is defined in a Java application server as a regular Web Archive and in an embedded server as a regular bundle. When it is hosted in an embedded server, it can be configured to not require a local disk. Why two versions? To enhance granularity. If you want to deploy PageBoxes on an Intranet or Extranet, just use the Application Server version. Why PageBox?
Today we have the choice between client/server and Web applications: With PageBox, we develop Web Applications but we deploy close to the client. It is a bit like cellular phone. A PageBox is a cell and we define more or less cells for an area depending on the number of clients (subscribers). With PageBoxes, presentation calls the central business logic and database access at least one time per page. If the presentation stays close to the business logic, isn't it faster?
If the presentation runs in the same JVM as the business logic, we spare EJB and JMS invocations on the wire but we must generate and send HTML whose volume is four to ten times bigger on our central system. We believe HTML processing is not the most efficient way to use large computers. Their value relies in their ability to process a large number of concurrent requests on a single RDBMS. We think they should only be used to support Web services. PageBox allows minimizing the number of roundtrips to the Central Systems: How can we administrate and troubleshoot remote presentation?
Through HTTP! As a PageBox is a HTTP server, it is much simpler to administrate than a fat client. The current JSPservlet implementation offer the following facilities: What is the publisher?
The value of PageBox is that it allows deploying presentation on a large number of inexpensive hosts. If we use PageBoxes we need to connect to each of them to make updates, a time-consuming process. Publisher is a tool to automate that process. We connect to a single point, submit an archive update and the tool takes care to distribute the update to all PageBoxes it knows. We distinguish the following roles: The editor hosts a PublisherServer and the content provider uses a PublisherClient to submit its presentation. What is the configurator? Configurator is a helper tool that aims to simply the remote installation of a PageBox or of a publisher. Configurator is a set of servlets that you install on the remote PageBox or publisher host. It checks your parameters and installs the PageBox or publisher. What is the mapper?
Thank to PageBox and Publisher your presentation is deployed on many hosts but your users know a single URL, so a single PageBox - or PageBox set if you use for instance DNS round-robbin. The mapper is a component embedded in PageBoxes able to route your users to the closest PageBoxes. How does it work? What is the library support?
Thank to the Publisher you can deploy the same presentation on many PageBoxes but it is only valuable if all PageBoxes provide the same consistent set of libraries that you used to develop the presentation. Library support provides such a facility. It already supports Xerces, Xalan and Apache Soap (both client and server). However it is primarily focused on Publishing frameworks. It already supports Cocoon.The reason is that Publishing frameworks ideally complement PageBox as they allow generating device-dependent flow without programming. A Publishing frameworks generates the data flow using a pipeline of: We complemented Cocoon with Network processors. Like a regular processor a Network process receives a document, changes it and returns the resulting document. However instead of transforming a document like XSLT, it:
You can combine regular and network processors as you want in a pipeline. What is the PageBox licence? PageBox implementations are Open Source. But the graphical Publisher client that is under GNU General Public License, all components were developed under GNU Lesser General Public License. The reason is that the General Public License does not permit incorporating our program into proprietary programs. As we want to grant you the right to host PageBox in proprietary application servers and also to use proprietary libraries and product within PageBox, we chose to license PageBox in the less restrictive GNU Lesser General Public License but PublisherClient, which is not a library but a standalone application. In both cases it means that we state that PageBox is copyrighted; and we add distribution terms, which are a legal instrument that gives everyone the rights to use, modify, and redistribute PageBox code or any program derived from it but only if the distribution terms are unchanged. What are the next steps?
Other FAQs Rationale
Presentation News
Faq Dev site
Mailing lists Home |