Timeline for OBSOLETE - Stack Overflow ebooks for Kindle
Current License: CC BY-SA 2.5
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 16, 2011 at 9:01 | comment | added | systempuntoout | @Adrian let me know if you need a hand | |
Feb 16, 2011 at 8:42 | comment | added | Adrian Petrescu | @systempuntoout I don't even think there's much use in notifying the user that the process is complete, since there's still an nondeterministic amount of time left until the file is actually sent to the device by Amazon through the e-mail address. I think the request can just automatically return "Your book will appear on the device shortly" and if this fails somewhere for some reason, we can send an error message/trace as the document instead. As you say, the hard part will be adapting his code to work on GAE :) I will look into that tomorrow, hopefully. I'm pretty optimistic though! | |
Feb 16, 2011 at 8:31 | comment | added | systempuntoout | @Adrian of course you can and each task on the task queue is not limited to 30 seconds but 10 minutes. I think that Channel API would help in this case: 1. User clicks on the Id question he/she wants 2. The process is started in the background using the taskqueue 3. User is asynchronously notified by the channel API that the process is complete. The first thing to check is that all the Python libraries used by Greg could be adopted on GAE considering that GAE does not allow write to file-system for example. | |
Feb 16, 2011 at 8:26 | comment | added | Adrian Petrescu | Actually, I just checked the relevant docs, and the timeout for Tasks in a Task Queue in the 1.4.0 API is ten minutes, not 30 seconds (which is the limit for a request to return). Since sending the document through e-mail can be done asynchronously, this is totally acceptable. | |
Feb 16, 2011 at 8:21 | comment | added | Adrian Petrescu | @systempuntoout Correct me if I'm wrong, but I think tasks on a task queue can add more tasks to the task queue. So as long as each individual step can be completed in 30 seconds I can just have a pipeline of tasks until the whole thing is assembled. In fact, if even they can't, you can still get the same effect by creating all the task queues at the same time and having the later stages fail until the output from the previous stages is present in the Datastore. I guess my point is I don't think the 30-second limit is too much of a limitation in this case. | |
Feb 16, 2011 at 7:56 | comment | added | systempuntoout | @Adrian I don't think Google App Engine could generate this on-the-fly, in 30 seconds you have plenty of things to do like fetching the data from SE, fetching the images, formatting the data to mobi etc.etc. . | |
Feb 16, 2011 at 0:57 | history | answered | Adrian Petrescu | CC BY-SA 2.5 |