It seems like a pretty good approach to me.
One thing to watch out for is that things can vanish from the memcache
(due to memory pressure). Don't assume it's going to be a reliable
storage mechanism! If you're OK with possibly losing events, then
it's OK, but if you require all events to for s
Thanks Tony. You are correct about the reliability issue with
memcache. Messages could be lost due to eviction. There might also be
coherence issues. If these start to become a deal-breaker then I will
look at using the data store and/or gae-utilities' Cache class as the
mechanism for storing mess
Let's not be tied to any one thing. Consider something like amazons queue
service?
On Nov 5, 2008 12:44 PM, "slmnhq" <[EMAIL PROTECTED]> wrote:
Hi,
I'm starting to build an interactive application where an event (eg:
mouse click) in one user's browser needs to trigger another event (eg:
show
Thanks Calvin. I read the docs for AQS and it looks worthwhile, not to
mention cheap too.
Thanks for mentioning this.
On Nov 6, 12:24 am, "Calvin Spealman" <[EMAIL PROTECTED]> wrote:
> Let's not be tied to any one thing. Consider something like amazons queue
> service?
>
> On Nov 5, 2008 12:44 PM
You mentioned using gaeutilities, and I thought I'd point out that you
could also use the session utility from that project for your session
ids as well. I'm not sure the overhead of the urlfetchers for AQS (as
well as the monetary costs) would be better than using Cache. Cache
will keep your data
