If I was new to Lift and saw a lift-util module and a lift-base module and had to guess which did not depend on anything web related, I would probably pick lift-util without hesitation. After all, "lift" is the name of a web framework, and "lift-base" implies that it's basic but central classes etc. "lift-util" sounds like utilities that are useful to lift, even necessary, but not central to what lift is. Many libraries have a "util" that has code with broad applicability but that needed to be packaged with the library because it relies on it and it wan't worth it to get the functionality elsewhere. So if it's an option I would move the web-related functionality to lift-base and leave Box and Actor etc. in lift-util.
------------------------------------- David Pollak<[email protected]> wrote: On Mon, Sep 28, 2009 at 10:47 PM, Heiko Seeberger < [email protected]> wrote: > What's the reason to have a new module (lift-base)? Why not put Actor to > lift-util and keep Box where it is? Because there are a lot of web-related things in lift-utils. I am going to for a separate package that is far more generic. > > In your branch def !?(timeout: Long, param: T) will return an Option. > Shouldn't this be a Box? > > Heiko > > 2009/9/29 David Pollak <[email protected]> > > Folks, >> >> Given the continued instability of Scala Actors, I've decided to remove >> them from Lift. >> >> Specifically, I'm migrating CometActors to sit on top of Lift's Actors. >> But, you'll also be able to use Akka Actors to power Lift's CometActors. >> Specifically, I'm working with Jonas to make sure that we share a common >> interface to Actors. >> >> I've gotten Lift nearly completely migrated over to Lift's Actors on the >> dpp_wip_actorize branch. See >> http://github.com/dpp/liftweb/tree/dpp_wip_actorize >> >> There will be some breaking changes to your applications. Specifically: >> >> - Box will be moved to a new package, net.liftweb.base (this is where >> the interface for Actors will live as well) >> - If you make any assumptions about your CometActors being Scala >> Actors (e.g., using linking), you will have to rewrite this code >> - Some methods in Lift that currently take Scala Actors as parameters >> will take Lift Actors (e.g., ActorPing) >> >> There will be a parallel Maven repository with the new Lift Actor stuff in >> it so you will be able to build you apps against the new code before the >> official switch-over. >> >> Milestone 6 (which should be out next week) will be based on the existing >> Actor model. After we get feedback from the community about the new Actor >> stuff, we will switch -SNAPSHOT over to the new Actor stuff. >> >> Questions, thoughts, or comments? >> >> Thanks, >> >> David >> >> >> >> -- >> Lift, the simply functional web framework http://liftweb.net >> Beginning Scala http://www.apress.com/book/view/1430219890 >> Follow me: http://twitter.com/dpp >> Surf the harmonics >> >> >> > > > -- > Heiko Seeberger > > My job: weiglewilczek.com > My blog: heikoseeberger.name > Follow me: twitter.com/hseeberger > OSGi on Scala: scalamodules.org > Lift, the simply functional web framework: liftweb.net > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
