[Opensource] Future Code for Expresso 5.1 and beyond [LONG THINK TANK ARTICLE]

[Kris Thompson]

> >
> > I have worked with RMI in the past and found it unsatisfying
> and would like
> > to recommend a JMS server solution but to be fair in my vote, I
> have never
> > worked with JMS before so it might be just as much or more of a
> pain then
> > RMI.  Any comments from folks who have done a JMS
> implementation, would this
> > be a good use of JMS?
> >
> > Kris
>
> A JMS solution would presuppose the existance of open source JMS Provider
> solution. JMS is rather like J2EE application server somebody has to
> write the back end solution, because JMS is just a standard
> API wrapper to enterprise information systems.
>
> However if the JobHandler was refactered to use a plugable implementation,
> using an interface, as described in the new design above,
> then I can not  see why JMS Job Handler would not work for those
> software houses with the ££££$$$$.

Whether it is refactored into a plugable implementation or not, this team
will still have to come up with at least one implementation and from what I
have seen so far and with my own experience I would suggest an RMI
implementation.

But I'm not so concerned with debating which implemenation we go with, seems
like we should focus on what this API might look like for that
implemenation..... along with general refactoring/fixing of the current Job
Handler.

Where can we find a list of the known Job Handler bugs?  How do we divide
the work on this component?

Kris

>
> --
> Peter Pilgrim
> ServerSide Java Specialist
>
> My on-line resume and for interview videos about myself, J2EE
> Open Source, Struts and Expresso.
>     ||
>     \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''
>
> _______________________________________________
> Opensource mailing list
> Opensource at jcorporate.com
> http://mail.jcorporate.com/mailman/listinfo/opensource
> Archives: http://mail.jcorporate.com/pipermail/opensource/
>