On Sep 21, 5:30 pm, David Pollak
wrote:
> Threads are used in Scala actors, but only while processing a message (actor
> jobs are allocated to threads in a thread pool). In the case of asking your
> external ad server for information, Scala Actors are not going to help you
> because they have no
On Sep 21, 4:29 pm, David Pollak
wrote:
> Well.. there's a Java way of doing exactly that: fork/join on a thread.
> Seehttp://java.sun.com/javase/6/docs/api/java/lang/Thread.html
>
> But to weave this into the page rendering, there would be some work required
> on your part: forking the threads
On Sep 21, 2:33 pm, David Pollak
wrote:
> Lift only uses event-based Actors for supporting CometActors. All parts of
> the standard HTTP request/response cycle (except for the CometActors) are
> handled on a single thread.
Hi David -
Thanks for your quick response. If an app developer wants to
I have been researching Web frameworks that will take advantage of
multi-core chips, and I'm trying to get a picture for how Lift uses
Scala's event-based actors for incoming page requests and how an
application developer would use actors in Lift to make concurrent Web
service or DB requests.
>Fr
on
I suspect that many of the maven packages are not current for the
various distributions so it would probably be beneficial to update the
Lift download instructions to reflect this.
James Thornton
[ja...@fedora espeed]$ mvn -e archetype:generate
/usr/lib/jvm/java
+ Error stacktraces are
