On Saturday, December 29, 2001, at 11:22 AM, Paul Hammant wrote:
Great. Do you mean port (as in fork) or migration.

Migration.

As part of the porting effort, we'll need to convert a handful of
specific entities in the Xindice tree that were implemented as part of
the Juggernaut framework:

  - Services
       HTTPServer (May modify this to be Servlet-based)

This sounds cool. Is there any chance this could ultimately be made a seperate Phoenix block? If lightweight, it could be a deployment choice for assemblers.

This is a possibility. The code for the service itself is very minimal and modular... All method handling is dispatched. Take a look at org.apache.xindice.server.services.HTTPServer for the source code.


This is where a gradual refactor approach could help. If you strive towards "beanification" where by the configurable component has multiple setter methods for configurable things, followed by an initialize() and start() invocations, then you'l be ready for allowing Phoenix to 'decorate' the server components block with configuration details, that it has retreieved from XML.

These patterns have been part of Juggernaut since the very beginning, so it should be pretty straight-forward.


As in code permissions or user authentication, authorisation and administration (AAA) or measures to prevent hacking and malicious code within the Phoenix machine?

Authentication and Permissioning.

Incidentally, take a look at http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/armi/
It is something that is based on work in AvalonDB and overlaps a little with your recently announced "Labroador". I am going to ask Peter Donald to consider it for use internally in Phoenix for inter-application comms.

It looks interesting, but is a pretty grandiose undertaking. I'll take a deeper look to see if there is any overlap or synergy. If we only even support SOAP and XML-RPC in Labrador, I'd be very happy.


--
Tom Bradford - http://www.tbradford.org
Chief Architect - The dbXML Group, L.L.C.
Developer - Apache Xindice (formerly dbXML)
Maintainer - jEdit-Syntax Java Editing Bean
Co-Author - O'Reilly's "Learning Xindice"



Reply via email to