Dear Alan,

As my dear BDFL says in
http://groups.google.com/group/liftweb/browse_thread/thread/f789cc5cb304ea52?pli=1

" I have worked out a mechanism for
thread-piggy-backing such that if the Actors are running in GAE, they need
not use any additional thread (this will enable Lift's comet support in
GAE.)  There will also be a scheduler (much like the existing ActorPing)
which will send a message to an Actor at some time in the future (and on
GAE, this scheduler, the Pinger, will not require a separate thread.) "

So basically GAE + lift should be just fine.



Yarr! ScalaWags!,

Viktor Klang

On Tue, Jun 2, 2009 at 4:47 PM, Scot <[email protected]>wrote:

>
>
> > Any recommendations?  I wonder which language Dick (I love the Groovy)
> > Wall would pick here...  I recall on the podcast Scala Lift having some
> > issues due to the lack of thread support in the app engine.  Is Groovy
> > therefore the right way to go?  Does it make walking XML parse trees
> > easy, along with generating a new resultant XML document?  Or are both
> > languages "fine choices".  I wanted to keep the project simple.
> >
>
> Groovy would probably be simpler than Scala. You could use Groovy's
> XMLSlurper to pull the the data you need out of your XML using GPath
> style expressions and probably avoid the need for recursion.
>
> Scala's builtin  XML processing facilities are powerful, but I found I
> needed to understand several other concepts in the language before I
> could really get to grips with ripping XML apart (there's a reason why
> XML processing is Chapter 26 of Programming in Scala). Oddly, you
> might find yourself not using recursion at all (or not that much),
> instead you could end up primarily using pattern matching with
> extractors. No matter what, you will probably have to write more code
> in Scala than in Groovy (at least that's what I've found). Saying
> that, I'd choose Scala over Java for processing XML any day.
>
> Out of interest, how are you going to generate the HTML? Are you going
> to use templates, or are you planning to generate the HTML in code?
> Again, the approach will be different depending on which language you
> choose. Groovy's builders are quite different from Scala's native XML
> support (and if you use Scala's XML, you're probably going to be
> generating XHTML like lift does).
>
>
> Scot
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The 
Java Posse" 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/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to