Interesting view point... Lift has very good support for managing HTTP requests, so, by default - REST. Im currently writing a series of posts about various components in Lift and dispatching / rest was the next one on my list. Probably get around to writing it next week.
Cheers, Tim On May 7, 9:29 pm, glenn <gl...@exmbly.com> wrote: > You are probably correct about Sling's overall usefullness. I was > thinking in terms > of Slings native restful capabilities more so than Jackrabbit, without > fully realizing that lift can do REST as well. > Is there documentation, or a sample, that can show me how to use it? > Here, the lift book is only > partially helpful. There is an example of JSON form handling, but > that's about it. Don't I need a REST server > that can handle the GET, POST, DELETE, etc. commands and work with the > the mapper objects? > > Glenn Silverman > > On May 7, 12:56 pm, David Pollak <feeder.of.the.be...@gmail.com> > wrote: > > > > > On Thu, May 7, 2009 at 12:23 PM, glenn <gl...@exmbly.com> wrote: > > > > Are there any thoughts about integrating lift with Apache Sling? There > > > is suppose to be a scala bundle that can be used in Sling, but I > > > haven't seen it. Does anyone know where to get it, or if it even > > > exists. > > > I took a look at Sling and see very little value in integration. Lift has > > the best REST handling out there. Multiple languages is a lose rather than > > a win. And anything that advertises itself as "fun" has an instance yellow > > flag from me. > > > > There would be a couple of reasons for wanting an integration - using > > > the Jackrabbit repository for all your lift-enabled html > > > Jackrabbit might be an interesting backing store for Lift and/or Lift > > content. It's pretty trivial to do this now with Lift. It's about 100 > > lines of code to use an external backing store for Lift content. > > > > and as an > > > alternative to a relational db for model persistence. In addition, > > > think of the mashups and gadgetization that would be possible with > > > lift OSGi bundles. > > > And we have an ongoing OSGi project within Lift, so an external one is not > > necessary. > > > > Obviously, a full integration would require changes to resource > > > management, but nothing that seems insurmountable. > > > If there was a compelling use case, I'd consider it more, but reviewing > > Sling, I can't seem to find one. I'm open to hearing thoughts on actual use > > cases. > > > Sorry. > > > David > > > > Glenn Silverman > > > -- > > Lift, the simply functional web frameworkhttp://liftweb.net > > Beginning Scalahttp://www.apress.com/book/view/1430219890 > > Follow me:http://twitter.com/dpp > > Git some:http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
