Re: Vision: JXTA Application Server for configuration & deployment
Vanessa Williams <[email protected]> Mon, 12 Jun 2006 11:38:44 -0400
| Newsgroups | gmane.comp.java.jxta.user |
|---|---|
| Message-ID | <[email protected]> |
There was a project called Tri-point that seems to have had some similar goals. It looks like it withered on the vine, though... No activity in a while. http://tripoint.jxta.org/ Vanessa On 11-Jun-06, at 6:58 AM, John Dickerson wrote: > Vision of where configuration and deployment of JXTA could go > ============================================================= > > Please let us all know if any of you share the same vision or > disagree with it. > > [A] JXTA applications are coded in a similar way to Servlet or EJB > applications. > > (i) When one creates a Servlet one does not have to code the Web > Container or the Application Server the Web Container sits in. > > Similarly when creating a P2P application one will only have to > code one or more JXTA services that make up the P2P Application. > > (ii) The P2P applications are zipped up in a p2p application jar > format; rather like a J2EE application is zipped up as an ear > application file with an ear extension. > > (iii The p2p application jars will have all the necessary > deployment xml files required to deploy the application: > > e.g. profile.xml file > e.g. services.xml file which maps logical names for services to > the class name implementing the services > > (iv) The P2P applications are hot deployable: One can drop the p2p > application jar under a deploy directory and the JXTA application > server will notice that this has occured and will deploy the > application. For example JBoss, a J2EE Application Server has a > hot deployable directory. > > > [B] Implications > > (i) The great thing about the JXTA application server concept is > that it could allow the life cycle of P2P applications to be > controlled. > > For example: > > (i) Band width allowed for JXTA application > > (ii) Local resources allowed for P2P application > (a) Hard Disk > (b) Memory requirements > (c) Processing Power > > (iii) Security Sand Box for non trusted applications > > (iv) Life span of P2P application > > (v) Management of multiple P2P applications on the same > machine > > (ii) JXTA application servers make it easier to integrate P2P > applications with other information systems. > > (iii) JXTA application servers make JXTA P2P a more serious > proposition to the corporate world and consequently encourage > JXTA's popularity as a serious alternative to .NET and J2EE for > certain application types. > > I am very excited by the JXTA Application Server vision as I > believe it can make JXTA easier to use and will also bring JXTA > into the mainstream alongside J2EE and .NET. > > Thank you all for your attention. > > Any criticisms or points of agreement you have with the JXTA > application server vision wil be much appreciated. > > Regards > > John Dickerson > > -- > > > "Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ... > Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Vanessa Williams Oponia Networks [email protected]