On Jun 10, 7:27 pm, Alex Boisvert <[email protected]> wrote:
> On Wed, Jun 10, 2009 at 9:15 AM, Atsuhiko Yamanaka <
>
> [email protected]> wrote:
>
> > Hi,
>
> > On Thu, Jun 11, 2009 at 12:30 AM, David
> > Pollak<[email protected]> wrote:
> > > Unfortunately, no. In order to do this, we'd have to have a hard
> > dependency
> > > on Jetty. It may be possible to do an external continuations module and
> > you
> > > are encouraged to research this.
>
> > I agree with you that a hard dependecy on jetty is not acceptable.
> > I will research that.
>
> Or perhaps have some sort of pluggable factory for continuations so the hard
> dependency can be moved into an optional module? The factory class could be
> configured in web.xml as a servlet init-param.
I think that the less XML config things are there, the better. We can
simply have a trait and the specific implementation will be packaged
in a separate jar.file that can just exist is a "by convension"
location. Say 'plugins' folder. With a very simple classloader we can
easily achieve this flexibility (... I don't thing that this is a
candidate for OSGI plugins).
>
> alex
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
