Re: [google-appengine] Re: Attempting to guarantee a write

2011-03-04 Thread Stephen
On Fri, Mar 4, 2011 at 12:26 AM, Richard Arrano rickarr...@gmail.com wrote: I had an idea that it might be able to be implemented in the form of something along the lines of 1MB unevictable memcache storage; You could do this with a persistent server:

[google-appengine] Re: Attempting to guarantee a write

2011-03-04 Thread stevep
Richard wrote: Something that occurred to me that might help you was I was actually considering de-isolating the datastore as a single point of failure by additionally sending out those really high importance writes via XMPP to some other server. Absolutely agree. Amazon Web Services is perfect.

[google-appengine] Re: Attempting to guarantee a write

2011-03-03 Thread Richard Arrano
Hello Robert, I don't necessary even need to do it by tasks - what I'm doing is something along the lines of a live ebay type auction, where I need to guarantee that when user X wins the bid for product Y, I will a) record this bid, b) be able to access it for the next item so I can know that

[google-appengine] Re: Attempting to guarantee a write

2011-03-03 Thread Ernesto Karim Oltra
Have you tried to implement some kind of status model in the db? Save the info in datastore. and call the tasks. Then the task could go see the data stored and check if it must confirm the bid, quit the task, send confirm e-mails, or things like that. On 3 mar, 08:52, Richard Arrano

Re: [google-appengine] Re: Attempting to guarantee a write

2011-03-03 Thread Robert Kluin
Hey Richard, I think your idea sounds good. Inserting a named task if you can't update the auction/item ought to do the trick. If your task gets into the queue it should run; you can also adjust your retry parameters if you want finer control of how tasks will retry. Any named task will

[google-appengine] Re: Attempting to guarantee a write

2011-03-03 Thread stevep
Hi Richard, Thought I'd comment since I started this thread. Think Wim and Robert have helped already more than I could. So just some thoughts from me. First: I hope any GAE engineers reading this thread might have a thought sparked about task queue featured needed for highly important,

[google-appengine] Re: Attempting to guarantee a write

2011-03-03 Thread Richard Arrano
Hi Steve, I would certainly agree about some sort of ability to guarantee low- volume high-importance storage. I had an idea that it might be able to be implemented in the form of something along the lines of 1MB unevictable memcache storage; we wouldn't be able to store much there, but we would

Re: [google-appengine] Re: Attempting to guarantee a write

2011-03-03 Thread Robert Kluin
Richard, I would also love to see the ability to query a list of tasks-to-be-executed. You can star issue 1790. http://code.google.com/p/googleappengine/issues/detail?id=1790 Robert On Thu, Mar 3, 2011 at 19:26, Richard Arrano rickarr...@gmail.com wrote: Hi Steve, I would