async uploading/replacing
|
March 07, 2011, 03:40 PM
|
|
Does 23 support asynchronous uploads/replaces as described in http://www.flickr.com/services/api/upload.async.html
For v.2 of my plugin I'm considering streamlining the process a lot by doing async processing. This moves the work back onto the users computer, and doesn't hold the same net connection open for a potentially long time.
---
Oops. I just saw that photos.upload.checkTickets is a dummy, so I think I can assume this is not the case.
|
| |
|
Team 23
March 07, 2011, 03:44 PM
|
|
Unfortunately not, there was some reason why we chose not to implement it - but frankly it escapes me now. Think you could probably emulate the async nature by simply killing the connection online all data has been sent though.
|
| |
|
|
March 08, 2011, 02:33 PM
|
|
Ideally we would want to be able to get the ticket back from the async call immediately so we could do a multi-threaded or coroutine consumer-producer model to make sure everything actually got uploaded. We just build a list of tickets, and check them to see if they were uploaded, failed or in progress.
This is, admittedly, a pretty advanced feature for what is essentially a simple upload tool. But I can see why people complain uploaders (to any site that uses REST or POST commands) can be slow operating on large sets.
It would also be very hard to debug :)
|
| |
|
