So the engineering team is not aware of any changes that might lead
to an extra few seconds delay in between the time the video is
uploaded and when it appears in the uploads feed. So there's nothing
that they could think of that would resolve what you're reporting.
As for an option for non-302 responses following browser-based
uploads, they were receptive to the idea, but it's not something that
they can actively work on at the moment. I wouldn't be surprised to
see it implemented in the future, though.
Cheers,
-Jeff Posnick, YouTube API Team
~ YouTube is hiring! ~ http://google.com/jobs/workyoutube ~
On Feb 25, 3:39 pm, Jeffrey Posnick <je...@google.com> wrote:
> Hello Jon,
>
> Thanks for the reference to the Amazon S3 approach. I'll see what the
> core engineering folks have to say about the feasibility of adding an
> optional parameter to force a 20x response.
>
> And I'll let you know if the team comes back with any explanation for
> added latency in keeping the uploads feed up to date.
>
> Cheers,
> -Jeff Posnick, YouTube API Team
> ~ YouTube is hiring! ~http://google.com/jobs/workyoutube~
>
> On Feb 25, 1:16 pm, Jon Drukman <jdruk...@gmail.com> wrote:
>
>
>
>
>
>
>
> > The real solution for the second part would be to have the response
> > from the upload server not be a 302, but rather a 200 with the video
> > id in the body of the response. This could be controllable via a
> > header in the original request, or a post variable in the request
> > body. This is how Amazon S3, which has a similar HTTP POST upload
> > API, works around this limitation in Flash. (See:http://docs.amazonwebservices.com/AmazonS3/latest/API/index.html?REST...
> > - look for "success_action_status")
>
> > As for the latency - as i said, this is new behavior, and it's
> > documented in the official docs that uploads are available
> > *immediately* in the upload feed. It used to be completely
> > synchronous, but something has changed recently so that is no longer
> > the case. Obviously, I'd prefer it if the original behavior was
> > restored, but if not, then at least the docs should be updated to
> > reflect the new behavior.
>
> > Personally, I'd prefer it if you implemented the 200 or 201 success
> > code as an option instead of the 302... That would obviate this entire
> > mess and simplify life greatly for all Flash developers. Surely you
> > want to make life easier for Flash developers, their lives are already
> > hard enough :)
>
> > -jsd-
>
> > On Feb 24, 2:08 pm, Jeffrey Posnick <je...@google.com> wrote:
>
> > > Hello Jon,
>
> > > I wish there were a good answer to the second part, but you're
> > > bumping up against a limitation in Flash here, and I don't know that
> > > Adobe has any plans to change things.
>
> > > Regarding the first part, I can understand why the delay is tripping
> > > you up and will let the engineering team know. If you're only seeing a
> > > latency of a couple of seconds then I'm not entirely sure what they'll
> > > be able to do (even if it used to be instant), but we'll see.
>
> > > Cheers,
> > > -Jeff Posnick, YouTube API Team
> > > ~ YouTube is hiring! ~http://google.com/jobs/workyoutube~
>
> > > On Feb 24, 1:56 pm, Jon Drukman <jdruk...@gmail.com> wrote:
>
> > > > Hi Jeff.
>
> > > > We are using the following URL to retrieve the user's upload feed:http://gdata.youtube.com/feeds/api/users/default/uploads
>
> > > > With AuthSub authentication, if it matters.
>
> > > > As I say, it seems like uploads used to be atomic - as soon as the
> > > > upload was complete, it would be visible in this feed (as
> > > > documented). Now there is a delay. It's usually just a few seconds,
> > > > but that's just enough to be troublesome.
>
> > > > Any thoughts about the second part of my original request: "Is there
> > > > any way we can get a direct upload method that returns the
> > > > video id in a fashion that Flash can actually see it?" That would
> > > > make the app logic so much simpler.
>
> > > > Let me know, thanks!
> > > > -jsd-
>
> > > > On Feb 22, 1:33 pm, Jeffrey Posnick <je...@google.com> wrote:
>
> > > > > Hello Jon,
>
> > > > > Before I escalate to the core engineering team, could you let me know
> > > > > whether you're using any query parameters when requesting the user's
> > > > > uploads feed? Some query parameters, like "orderby", necessitate a
> > > > > lookup against an index of videos rather than the raw feed of the
> > > > > user's upload activity, and that index will almost always be staler
> > > > > than the raw feed.
>
> > > > > Cheers,
> > > > > -Jeff Posnick, YouTube API Team
> > > > > ~ YouTube is hiring! ~http://google.com/jobs/workyoutube~
>
> > > > > On Feb 18, 6:20 pm, Jon Drukman <jdruk...@gmail.com> wrote:
>
> > > > > > We have been using Flash to upload direct into youtube. As you know,
> > > > > > when the upload finishes, Youtube sends a 302 redirect with the video
> > > > > > ID. Flash is unable to read the contents of the 302 redirect so it's
> > > > > > impossible to get the video id.
>
> > > > > > Our current solution is to add a developer tag to the upload, then
> > > > > > grab the user's upload feed and check for the first video with that
> > > > > > tag. This was working fine until recently. The documentation athttp://code.google.com/apis/youtube/2.0/developers_guide_protocol_che...
> > > > > > states "An uploaded video will immediately be visible in an
> > > > > > authenticated user's uploaded videos feed." This used to be true but
> > > > > > it doesn't appear to be the case any more. We are retrieving the
> > > > > > user's feed as soon as the upload completes and the video does not
> > > > > > appear in the feed. I'm going to have to write a loop to try grabbing
> > > > > > the feed over and over again until it shows up, which is really crappy
> > > > > > for so many reasons.
>
> > > > > > Is there any way we can get a direct upload method that returns the
> > > > > > video id in a fashion that Flash can actually see it?
>
> > > > > > Thanks
> > > > > > -jsd-
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment