The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

NAME

WebService::GData::YouTube::Doc::BrowserBasedUpload - YouTube Video browser based upload system

SYNOPSIS

    use WebService::GData::YouTube;
    
    #set your key obtained via the dashboard
    
    use constant KEY=>'*****r*****************s**************B*';
    
    #connect to an account via ClientLogin
    
    my $auth; 
    eval {
        $auth = new WebService::GData::ClientLogin(
                email=>'********@gmail.com',
                password=>'*********',
                key=>KEY
        );
    };
    
    #handle error
    
    if(my $error = $@){
       #do something meaningful
       #$error->code,$error->content
    }

    #create an empty video placeholder with read access
    
    my $video = new WebService::GData::YouTube($auth)->video;

    #set the data (from a form for example):
    
    $video->title('Live at Shibuya tonight');
    
    $video->description('Live performance by 6 local bands.');
    
    $video->keywords('music','live','shibuya','tokyo');
    
    $video->category('Music');
    
    #from google map for example
    $video->location('0.12121452 0.232323525');
    
    #who can see me?
    $video->is_private(1);
    
    #all the available settings can be set
    $video->access_control('comment','allowed');
   
    #make the request
    
    my($url,$token);  
    eval {
      ($url,$token)= $video->save();
    };
    
    if(my $error = $@){
        #do someting meaningful
        #$error->code,$error->content
    }

        #url encode with your favorite module before sending it:    
        
    my $nexturl = 'http://www.example.com/thankyou.html';
    
    #create a form and display it
    #the token and file as input name is a requirement
    #as is the nexturl parameter
    
    my $form = <<FORM;
    
    <form action="$url?nexturl=$nexturl" method="post" enctype="multipart/form-data">
         <input id="file" type="file" name="file"/>
         <input type="hidden" name="token" value="$token"/>
         <input type="submit" value="upload" />
    </form>
    
    FORM
    
    #once uploaded, YouTube redirect the user to your nexturl parameter.
    #it can look like the url below if everything went fine:
    
    http://www.example.com/thankyou.html?id=sxZekqqleksk&status=200

    #or something went wrong:
    http://www.example.com/thankyou.html?status=403&code=INVALID_TOKEN 

DESCRIPTION

!WARNINGS! Developer release. Starting refactoring. Low level API only available for now. Things may change or break but feel free to give me some feedbacks!

    Browser-based uploading is one of the mechanism that allows you to upload a video to YouTube.

    It is ideal if you do not want to host the video on your server.

GENERAL OVERVIEW

    Browser-based uploading is a 5 step mechanism:

    * First get the meta data of the video (title,description,keywords...)

    * Send to YouTube the meta data with authorization headers

    * If it successfully records your meta data, YouTube sends back an url and a token. This data is used to link together the meta data and the video file itself.

    * Present the user with a way to choose the video he/she wants to upload and send the data directly over YouTube.

    * If the upload process is finished (either success or failure), YouTube redirects your user to the url you've specified; with some extra parameters

    You can read an in-depth explanation of the process:

    http://code.google.com/intl/en/apis/youtube/2.0/developers_guide_protocol_browser_based_uploading.html#Browser_Upload_Process

AUTHENTICATION AND DASHBOARD

    In order to write data to YouTube, you must do two things:

    * Register an application to the YouTube Dashboard:

    http://code.google.com/apis/youtube/dashboard/

    By registering your application, you will get a unique developer key that will be required when doing any write actions.

    * Authorized the user to do write actions

    Saving meta data, updating meta data or uploading a file require to be authorized.

    Actually only ClientLogin mechanism is implemented in the library but OAuth will arrive soon.

    ClientLogin is by far the simplest authorization mechanism. Basically, you log in yourself into an account by giving email, password and your key and you get back an authorization key.

    OAuth requires some steps ahead before using it and we won't see them as long as the mechanism is not in place.

ClientLogin and Developer key

    In order to be authorized you must log in into an account. You can do so by using WebService::GData::ClientLogin.

    Example:

        #key from your dashboard
            
        use constant KEY=>'*****r*****************s**************B*';
        
        #connect to an account via ClientLogin
        
        my $auth; 
        eval {
            $auth = new WebService::GData::ClientLogin(
                    email=>'********@gmail.com',
                    password=>'*********',
                    key=>KEY
            );
        };
        
        #handle error
        
        if(my $error = $@){
           #do something meaningful
           #$error->code,$error->content
        }
        

    If everything went fine, you can create a YouTube instance with write access.

    See WebService::GData::ClientLogin for further details about the log in mechanism.

CREATING A VIDEO

    Now that you are logged in, you have to pass the authorization object to the YouTube instance:

    Example:

        use WebService::GData::ClientLogin;
        use WebService::GData::YouTube;
            
        #log in
        my $auth = new WebService::GData::ClientLogin(...);
    
        #create an empty video placeholder with read access
        
        my $video = new WebService::GData::YouTube($auth)->video;

    Now you have a place holder, it is just a matter of filling the proper information. You should create a form where the user would enter the following information(* specify an optional information):

    * Title of the video

    * Description of the video

    * Keywords

    * Category (predefined categories from YouTube: People,Music...)

    * Location* (longitude and latitude coming from a map, let's say Google Map)

    * Private* (if set to private only predefined user will be able to see the video)

    * Access Control* See http://code.google.com/intl/en/apis/youtube/2.0/reference.html#youtube_data_api_tag_yt:accessControl

    So it could be something like that:

    Example:

        use CGI;
        #create an empty video placeholder with read access
        
        my $video = new WebService::GData::YouTube($auth)->video;
    
        my $request= new CGI;
        
        $video->title($request->param('title'));
        
        $video->description($request->param('description'));
        
        $video->keywords($request->param('keywords'));
        
        $video->category($request->param('category'));
        
        #from google map for example
        $video->location($request->param('location'));
        
        #who can see me?
        $video->is_private(1) if($request->param('is_private'));
        
        #all the available settings can be set
        $entry->access_control('comment',$request->param('comment'));
        $entry->access_control('comment',$request->param('embed'));
        

SAVING VIDEO META DATA

    Now that we have all the meta information we need, let's save them:

    Example:

        use CGI;
        #create an empty video placeholder with read access
        
        my $video = new WebService::GData::YouTube($auth)->video;
    
        my $request= new CGI;
        
        $video->title($request->param('title'));
        
        $video->description($request->param('description'));
    
        ....
        
        my($url,$token)= $video->save;
       

    As you can see the save method sends back two variables: an url and a token. At this stage of the process, the meta information is stored as temporary information within YouTube. The $url and $token does expire after a certain amount of time (15 minutes it seems.)

SAVING VIDEO FILE

The above $url and $token variables must be used in the form that will be presented to the user to upload the video.

You must also set an url to go back to your site once the upload process is finished. You do so by adding ?nexturl=http%3A%2F%2Fwww.example.com after the $url. As you can see the url must be encoded.

Example:

    my $nexturl = 'http://www.example.com/thankyou.html';#encode the url with URI::Escape for example
    
    #create a form and display it
    #the token and file as input name is a requirement
    #as is the nexturl parameter
    
    my $form = <<FORM;
    
    <form action="$url?nexturl=$nexturl" method="post" enctype="multipart/form-data">
         <input id="file" type="file" name="file"/>
         <input type="hidden" name="token" value="$token"/>
         <input type="submit" value="upload" />
    </form>
    
    FORM
    

HANDLING RETURNED VALUE

    The user has choosen his/her video, pressed upload.

    YouTube handled the request directly and will redirect to your website (well, to the url specified in nexturl) by adding some parameters defining the state of the video.

SUCCESSFUL UPLOAD

Example:

    http://www.example.com/thankyou.html?id=sxZekqqleksk&status=200
    

The id parameter is the newly created unique id for your video.

FAILED UPLOAD

Example:

        http://www.example.com/thankyou.html?status=403&code=INVALID_TOKEN 
        

If an error occurs, you will have to look into the status and code parameter and inform the user, log,etc.

SEE ALSO

AUTHOR

shiriru <shirirulestheworld[arobas]gmail.com>

LICENSE AND COPYRIGHT

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

7 POD Errors

The following errors were encountered while parsing the POD:

Around line 109:

You can't have =items (as at line 113) unless the first thing after the =over is an =item

Around line 134:

You can't have =items (as at line 138) unless the first thing after the =over is an =item

Around line 199:

You can't have =items (as at line 219) unless the first thing after the =over is an =item

Around line 295:

You forgot a '=back' before '=head2'

Around line 322:

=back without =over

Around line 334:

You forgot a '=back' before '=head3'

Around line 352:

=back without =over