On 20:59, Eelco Hillenius wrote:
It's probably a good idea to have a specialized implementation of
ISessionStore for App Engine that uses whatever makes sense with App
Engine for medium term storage ('cause that's what it is... short term
storage is the current page, which is typically local
Hi,
The Terracotta SecondLevelCacheSessionStore does not contain any Terracotta
specific implementation or dependencies, and should work fine on AppEngine
(I haven't tested it though).
All it is is an implementation of IPageStore, where the pages are serialized
to byte arrays (like the disk
On 20.10.2009 13:30, richardwilko wrote:
Hi,
The Terracotta SecondLevelCacheSessionStore does not contain any Terracotta
specific implementation or dependencies, and should work fine on AppEngine
(I haven't tested it though).
All it is is an implementation of IPageStore, where the pages are
andr,
From Wikipedia [1]:
The Apache License does not require modified versions of the software to be
distributed using the same license nor even that it be distributed as
free/open-source software. The Apache license only requires that a notice is
kept informing recipients that Apache licensed
Oh, sorry I just realized that it has the terracotta licence header on it,
had I realized i would have removed it. That's because the version of the
file i had to hand was from the terracotta forge svn repo, and code in there
has to have their licence.
Originally it was Apache 2 licensed and I
On 20.10.2009 14:48, richardwilko wrote:
Oh, sorry I just realized that it has the terracotta licence header on it,
had I realized i would have removed it. That's because the version of the
file i had to hand was from the terracotta forge svn repo, and code in there
has to have their licence.
Here's a minor point that tripped me up. I have my WicketFilter
mapped to a given path:
filter-mapping
filter-nameWicketFilter/filter-name
url-pattern/evansforlv/*/url-pattern
/filter-mapping
And then when I start up my local app and browse to
I've followed with interest all the wicket on GAE threads I can, and these
all seem to address necessary minor tweaks to get it set up, but the one big
thing I haven't seen much discussion on is the BigTable storage system,
since we wouldn't be able to use MySQL.
Maybe that's the whole point for
You can get a dedicated server at GoDaddy for under $100 per month.
I've had one running Java / Wicket apps with an uptime of around two
years now. With your very small load, you could also use
redwoodvirtual and use a Linux Virtual Server for $20 or $40. I also
had a server with them running
File uploads seem to be causing some problems. On Wicket uploaded
files are first written to some temporary file and on AppEngine this
is obviously not possible. I haven't yet investigated if it is easy to
change this behavior in Wicket. Another option might be to write a
separate servlet for just
Both articles avoid the DiskPageStore problem by using the HttpSessionStore,
however if you do a search through the mailing list archives for
HttpSessionStore you'll find numerous references to problems in using it in
the long term and especially in a real, production application, so I don't
Maarten Bosteels wrote:
But AFAIK GAE doesn't use/guarantee sticky sessions, so I am afraid
you can't rely on local memory.
App Engine uses multiple web servers to run your application, and
automatically adjusts the number of servers it is using to handle
requests reliably. A given request may
Good news:
http://groups.google.com/group/google-appengine-java/msg/f50bbb131dc524c1
quote
HttpSessions will work out of the box if you enable them in your
appengine-web.xml.
We do not guarantee that all requests for the same session go to the same
JVM, but persistence of sessions is managed
Here are a couple of pointers regarding Wicket on GAE:
http://www.danwalmsley.com/2009/04/08/apache-wicket-on-google-app-engine-for-java/
On Sat, Apr 11, 2009 at 6:15 PM, Matthew Welch matt...@welchkin.net wrote:
I've been experimenting a bit with Google App Engine and Wicket and things
seemed
Here's another article about Wicket and GAE on DZone:
http://www.dzone.com/links/rss/wicket_on_google_app_engine.html
On Sat, Apr 11, 2009 at 8:22 AM, Sergey Podatelev
brightnesslev...@gmail.com wrote:
Here are a couple of pointers regarding Wicket on GAE:
Both articles avoid the DiskPageStore problem by using the HttpSessionStore,
however if you do a search through the mailing list archives for
HttpSessionStore you'll find numerous references to problems in using it in
the long term and especially in a real, production application, so I don't
16 matches
Mail list logo
