[Lift] Re: Lift and Goat Rodeo
David Pollak a écrit : Folks, [...] Over the last couple of years, I've been noticing trends in web development, in the needs of my various consulting gigs, and in some other projects. It's clear to me that it's time for a unified data and data management model that goes beyond OR mapping and that is scalably transactional. I've put together a model that looks to the developer like STM but is backed with ZooKeeper and Cassandra. I've blogged about it at http://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-Such.html Just as my web framework manifesto was the genesis of what has become Lift, I hope that my notions and ramblings in this blog post will become concrete, usable code over the next few months and a solid platform for building the next generation of web systems over the next few years... all built with Scala at their core. Wow :) I hope this project will be as successful as lift... Its goals seem great ! -- Francois Armand http://fanf42.blogspot.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
This sounds very exciting David, please ensure to keep us posted on any developments. This notion of Q's - is this the method by which actors will be distributed (managed via zookeeper, i would assume)? Any reference materials you can point me to further whet my appetite? On Thu, 2009-06-18 at 00:19 -0700, David Pollak wrote: Folks, At the end of the Scala Lift Off, after I finished my third beer, Martin Odersky came over to me and asked, so, what's the future of Lift? I gave a hand-waving answer about the features for 1.1. But Martin is not a hand-waving kind of guy and I think I owe him and the other folks in the Scala and Lift communities more. There's a lot more that's necessary for web app development than Lift, an abstraction to the HTTP request/response cycle, can provide. Over the last couple of years, I've been noticing trends in web development, in the needs of my various consulting gigs, and in some other projects. It's clear to me that it's time for a unified data and data management model that goes beyond OR mapping and that is scalably transactional. I've put together a model that looks to the developer like STM but is backed with ZooKeeper and Cassandra. I've blogged about it at http://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-Such.html Just as my web framework manifesto was the genesis of what has become Lift, I hope that my notions and ramblings in this blog post will become concrete, usable code over the next few months and a solid platform for building the next generation of web systems over the next few years... all built with Scala at their core. 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
David, Amazing, I love your PASSION. All the best. Mohan From: liftweb@googlegroups.com [mailto:lift...@googlegroups.com] On Behalf Of David Pollak Sent: 18 June 2009 15:20 To: David Pollak Subject: [Lift] Lift and Goat Rodeo Folks, At the end of the Scala Lift Off, after I finished my third beer, Martin Odersky came over to me and asked, so, what's the future of Lift? I gave a hand-waving answer about the features for 1.1. But Martin is not a hand-waving kind of guy and I think I owe him and the other folks in the Scala and Lift communities more. There's a lot more that's necessary for web app development than Lift, an abstraction to the HTTP request/response cycle, can provide. Over the last couple of years, I've been noticing trends in web development, in the needs of my various consulting gigs, and in some other projects. It's clear to me that it's time for a unified data and data management model that goes beyond OR mapping and that is scalably transactional. I've put together a model that looks to the developer like STM but is backed with ZooKeeper and Cassandra. I've blogged about it at http://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-Suc h.html Just as my web framework manifesto was the genesis of what has become Lift, I hope that my notions and ramblings in this blog post will become concrete, usable code over the next few months and a solid platform for building the next generation of web systems over the next few years... all built with Scala at their core. 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 Git some: http://github.com/dpp == Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html == --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
Dave is there a reason why writes are allowed outside a transaction boundaries ? Br's, Marius On Jun 18, 10:19 am, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, At the end of the Scala Lift Off, after I finished my third beer, Martin Odersky came over to me and asked, so, what's the future of Lift? I gave a hand-waving answer about the features for 1.1. But Martin is not a hand-waving kind of guy and I think I owe him and the other folks in the Scala and Lift communities more. There's a lot more that's necessary for web app development than Lift, an abstraction to the HTTP request/response cycle, can provide. Over the last couple of years, I've been noticing trends in web development, in the needs of my various consulting gigs, and in some other projects. It's clear to me that it's time for a unified data and data management model that goes beyond OR mapping and that is scalably transactional. I've put together a model that looks to the developer like STM but is backed with ZooKeeper and Cassandra. I've blogged about it athttp://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-... Just as my web framework manifesto was the genesis of what has become Lift, I hope that my notions and ramblings in this blog post will become concrete, usable code over the next few months and a solid platform for building the next generation of web systems over the next few years... all built with Scala at their core. Thanks, David -- 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
David, that sounds really great. I tried to think about what's a good approach to be really scalable in context of data writing/reading (e.g. when you have to write an app for a huge number of users) A RDMBS approach would not be sufficient. Looking forward for further information for this subject. Regards, Martin On 18 Jun., 09:19, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, At the end of the Scala Lift Off, after I finished my third beer, Martin Odersky came over to me and asked, so, what's the future of Lift? I gave a hand-waving answer about the features for 1.1. But Martin is not a hand-waving kind of guy and I think I owe him and the other folks in the Scala and Lift communities more. There's a lot more that's necessary for web app development than Lift, an abstraction to the HTTP request/response cycle, can provide. Over the last couple of years, I've been noticing trends in web development, in the needs of my various consulting gigs, and in some other projects. It's clear to me that it's time for a unified data and data management model that goes beyond OR mapping and that is scalably transactional. I've put together a model that looks to the developer like STM but is backed with ZooKeeper and Cassandra. I've blogged about it athttp://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-... Just as my web framework manifesto was the genesis of what has become Lift, I hope that my notions and ramblings in this blog post will become concrete, usable code over the next few months and a solid platform for building the next generation of web systems over the next few years... all built with Scala at their core. Thanks, David -- 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
On Thu, Jun 18, 2009 at 4:23 AM, marius d. marius.dan...@gmail.com wrote: Dave is there a reason why writes are allowed outside a transaction boundaries ? Writes are not allowed outside of transactional boundaries. You have to enter a transaction to get a TRef, a transactional reference. You can only read or write via a TRef. Br's, Marius On Jun 18, 10:19 am, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, At the end of the Scala Lift Off, after I finished my third beer, Martin Odersky came over to me and asked, so, what's the future of Lift? I gave a hand-waving answer about the features for 1.1. But Martin is not a hand-waving kind of guy and I think I owe him and the other folks in the Scala and Lift communities more. There's a lot more that's necessary for web app development than Lift, an abstraction to the HTTP request/response cycle, can provide. Over the last couple of years, I've been noticing trends in web development, in the needs of my various consulting gigs, and in some other projects. It's clear to me that it's time for a unified data and data management model that goes beyond OR mapping and that is scalably transactional. I've put together a model that looks to the developer like STM but is backed with ZooKeeper and Cassandra. I've blogged about it athttp:// blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-... Just as my web framework manifesto was the genesis of what has become Lift, I hope that my notions and ramblings in this blog post will become concrete, usable code over the next few months and a solid platform for building the next generation of web systems over the next few years... all built with Scala at their core. Thanks, David -- 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 -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
On Thu, Jun 18, 2009 at 8:29 AM, TSP tim.pig...@optrak.co.uk wrote: Hi David, I am working in the typical business application space, where rdbms are quite nice solutions - lots of tables but in your application you never really need an awful lot of rows for anything other than consolidated reporting. What concerns me is that if the attention of the principal author of lift is on building systems for mega social networking activities that I really don't need, does that mean that other aspects of Lift development will fall by the wayside? if this is the case, will Lift still be a useful platform for my purposes? I may be wrong but I suspect most people's needs may be more prosaic. Tim, I'm not leaving Lift. Lift is a critical part of Goat Rodeo, but Goat Rodeo is necessary to span data and logic into the browser as well as the backing store. The concrete things you'll see out of me related to Lift in the next few months are: - Completion of the record package - Integration of jsync into Lift for better synchronization of client/server state (with a bunch of security enhancements) - Some componentization of display logic so you'll be able to define the JavaScript parts of your UI in a more declarative way - Wizard... the ability to define multi-screen input forms Plus, as Derek pointed out on another thread, this community totally rocks and I'm not going anywhere because I love the people and energy in the Lift community. I could have made Goat Rodeo part of Lift, but it's going to be another year or more before the Goat Rodeo APIs settle and I want to make sure that Lift APIs are more stable. So, no, I'm not going anywhere. In fact, I'm not traveling in Q3 or Q4 and I've got no book to write, so I'm much more focused on enhancing Lift, Lift-related technologies and contributing to the Lift community. Thanks, David PS -- btw, if I did get hit by a bus tomorrow, Lift would continue to grow and thrive. The existing Lift committers could take the project forward in spectacular ways. I may be the loudest mouth in the Lift community, but I am not the biggest brain or the best coder. Tim -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
Sorry Dave but something still escapes me. Transaction.write also takes a TRef parameter which is never used. Furthermore nothing seems to prevent one to call new TRef... outside a Transaction. I assume the normal usage is: val ref = new Ref(QString()) ref.map(tref = // do transactional reads and writes. Very cool) but then I can do: val tref = new TRef(ref) tref(QString(new val)) ... but this does not seam to be transactional since we're outside a transaction context? Perhaps TRef.set should call Transaction.write from a ref.map( ... ) as this gives transaction wrapping? Br's, Marius On Jun 18, 6:14 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Thu, Jun 18, 2009 at 4:23 AM, marius d. marius.dan...@gmail.com wrote: Dave is there a reason why writes are allowed outside a transaction boundaries ? Writes are not allowed outside of transactional boundaries. You have to enter a transaction to get a TRef, a transactional reference. You can only read or write via a TRef. Br's, Marius On Jun 18, 10:19 am, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, At the end of the Scala Lift Off, after I finished my third beer, Martin Odersky came over to me and asked, so, what's the future of Lift? I gave a hand-waving answer about the features for 1.1. But Martin is not a hand-waving kind of guy and I think I owe him and the other folks in the Scala and Lift communities more. There's a lot more that's necessary for web app development than Lift, an abstraction to the HTTP request/response cycle, can provide. Over the last couple of years, I've been noticing trends in web development, in the needs of my various consulting gigs, and in some other projects. It's clear to me that it's time for a unified data and data management model that goes beyond OR mapping and that is scalably transactional. I've put together a model that looks to the developer like STM but is backed with ZooKeeper and Cassandra. I've blogged about it athttp:// blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-... Just as my web framework manifesto was the genesis of what has become Lift, I hope that my notions and ramblings in this blog post will become concrete, usable code over the next few months and a solid platform for building the next generation of web systems over the next few years... all built with Scala at their core. Thanks, David -- 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 -- 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 -~--~~~~--~~--~--~---
[Lift] Re: Lift and Goat Rodeo
Yeah... I haven't sealed things yet. You can do these things... but not for long. ;-) On Jun 18, 2009 10:36 AM, marius d. marius.dan...@gmail.com wrote: Sorry Dave but something still escapes me. Transaction.write also takes a TRef parameter which is never used. Furthermore nothing seems to prevent one to call new TRef... outside a Transaction. I assume the normal usage is: val ref = new Ref(QString()) ref.map(tref = // do transactional reads and writes. Very cool) but then I can do: val tref = new TRef(ref) tref(QString(new val)) ... but this does not seam to be transactional since we're outside a transaction context? Perhaps TRef.set should call Transaction.write from a ref.map( ... ) as this gives transaction wrapping? Br's, Marius On Jun 18, 6:14 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Thu, Jun 18, 2009 at 4:23 AM, marius d. marius.dan...@gmail.com wrote:Dave is there a ... --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
