Chris suggests....
> That being the case I would recommend:
...and I concur for the most part.
> 1. We concentrate on the core Embedlet technology to let us quickly
> produce a standard with a demonstratable reference implementation.
This is probably going to take longer than anyone expects. Open source
development produces good product, especially for infrastructure/plumbing
applications, but it does take longer than you think.
> 2. We create a simple, flexible communication protocol that will
> accomodate any XML, TCP/IP capable system.
HTTP and XML out of the box! Yup! I vote for that!
> 3. We create demonstration GUI based configuration and monitoring tools.
> At least a JavaBean/Swing component that can be used as a bsisi for
> extension. This, I have found from experience, is the 'easy' part as long
> as the underlying technology is simple and directly exposed as it is in
> XML.
No problem there...this could easily be a separate but parallel subproject.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
|
