Please DO NOT send wso2 internal gdocs to architecture@ as external users
cannot read them

Thanks,
Samisa...


Samisa Abeysinghe

Vice President Delivery

WSO2 Inc.
http://wso2.com



On Thu, Jun 19, 2014 at 6:28 PM, Milinda Perera <[email protected]> wrote:

> Hi,
>
> Please find the attached milestone plan [1]
> <https://docs.google.com/a/wso2.com/spreadsheets/d/1H2N2-JSWRT3QTjEIqZZj2DctdBMRQdxxf5Z_ViqWySY/edit?usp=sharing>
> for the training project: ESB connector for Tumblr
> ​
>  Milestone Plan - Tumblr connector
> <https://docs.google.com/a/wso2.com/spreadsheets/d/1H2N2-JSWRT3QTjEIqZZj2DctdBMRQdxxf5Z_ViqWySY/edit?usp=drive_web>
> ​
> [1]
> https://docs.google.com/a/wso2.com/spreadsheets/d/1H2N2-JSWRT3QTjEIqZZj2DctdBMRQdxxf5Z_ViqWySY/edit?usp=sharing
>
> Thanks,
> Milinda
>
>
>
> On Thu, Jun 19, 2014 at 1:06 PM, Milinda Perera <[email protected]> wrote:
>
>> Hi dushan,
>>
>> This connector will cover all CURD operations on blog posts of all types.
>> Is it better to create separate methods to create, edit each post type?
>> like createTextPost, createAudioPost, createVideoPost ... etc.
>>
>> when comes to blog posts we can specify the type of the post by “type”
>> (text, photo, quote, link, chat, audio, video) request parameter in the
>> request.
>>
>> *text* posts:  full post body (html allowed) can assign to body request
>> parameter.
>>
>> *photo* posts: can add photo source url (source request parameter) or
>> url encoded binary content  (data request parameter) [limit:10MB]
>>
>> *audio/video* posts: can add using external url for *audio*
>> (external_url request parameter) and HTML embed code for the *video*
>> (embed request parameter) or url encoded binary content (data request
>> parameter) [limit:10MB for audio, 100MB for video]
>>
>> for now I'm planning only external url for audio and HTML embed code for
>> the video.
>>
>> The api documentation [1] does not provide http request message
>> information properly. So need to test api to identify proper http message
>> format for POST requests. I'm currently working on it.
>>
>> I will share project plan asap.
>>
>> [1] https://www.tumblr.com/docs/en/api/v2
>>
>>
>> thanks,
>> Milinda
>>
>>
>>
>>
>> On Thu, Jun 19, 2014 at 10:12 AM, Dushan Abeyruwan <[email protected]>
>> wrote:
>>
>>> Hi
>>>   I think you do cover all CURD operations related to post blogs
>>> (text,photo,queue,link,audio,video,answer) ? How audio/video upload happens
>>> ? have you done any background search ?
>>>
>>> anyway, looks good to me please do share Project plan across
>>>
>>> Cheers,
>>> Dushan
>>>
>>>
>>>
>>>
>>> On Wed, Jun 18, 2014 at 9:30 PM, Milinda Perera <[email protected]>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> **Introduction**
>>>>
>>>> Tumblr is microblogging, social networking and content sharing website.
>>>> Users are able to reblog, use multimedia (images, videos, sound clips)
>>>>
>>>> **API**
>>>>
>>>> Tumblr API [1] <https://www.tumblr.com/docs/en/api/v2>
>>>>
>>>> **Tumblr Connector Summary**
>>>>
>>>> • Connector Name:  tumblr-connector-1.0.0
>>>>
>>>> • Version: 1.0.0
>>>>
>>>> • Technology: REST
>>>>
>>>> **Authentication**
>>>>
>>>> Supports OAuth 1.0a protocol
>>>>
>>>> **Selected methods**
>>>>
>>>> General Blog Methods:
>>>>
>>>>
>>>>     getBlogInfo - retrieve general information about the blog (title,
>>>> number of posts, and other high-level data)
>>>>
>>>>     getBlogAvatar - retrieve blog's avatar
>>>>
>>>>     getFollowers - retrieve followers of the blog
>>>>
>>>>
>>>> Blog post Methods:
>>>>
>>>>
>>>>     getPosts - retrieve posts (can retrieve all posts, specified
>>>> number of posts, specific types of posts (text, quote, link, answer, video,
>>>> audio, photo, chat), or a post specified by the ID)
>>>>
>>>>     getQueuedPosts - retrieve queued posts
>>>>
>>>>     getDraftPosts - retrieve drafted posts
>>>>     getSubmissionPost ** - retrieve submission posts
>>>>
>>>>     createPost - create new blog post
>>>>
>>>>     editPost - edit existing blog post
>>>>
>>>>     reblogPost - reblog a blog post
>>>>
>>>>     deletePost - delete blog post
>>>>
>>>>
>>>> User Methods:
>>>>
>>>>
>>>>     getUserInfo - retrieve the user's account information that matches
>>>> the OAuth credentials submitted with the request
>>>>
>>>>     getUserDashboard - retrieve the dashboard
>>>>
>>>>     getUserLikes - retrieve the liked posts
>>>>
>>>>     getFollowingPosts - retrieve the blogs followed by the user
>>>>
>>>>     follow - follow a blog
>>>>
>>>>     unfollow - unfollow a blog
>>>>
>>>>     like - like blog post
>>>>
>>>>     unlike - unlike blog post
>>>>
>>>>
>>>> TaggedMethods:
>>>>
>>>>
>>>>     getTaggedPosts - get posts with a given tag
>>>>
>>>>
>>>>
>>>> getSubmissionPost** [2]
>>>> <http://staff.tumblr.com/post/138478782/submissions> still unable to
>>>> tryout (waiting for approval for the submitted post by moderator)
>>>>
>>>>
>>>> [1] https://www.tumblr.com/docs/en/api/v2
>>>> [2] http://staff.tumblr.com/post/138478782/submissions
>>>>
>>>>
>>>> Thanks,
>>>> Milinda
>>>>
>>>>
>>>>
>>>> --
>>>> Milinda Perera
>>>> Software Engineer;
>>>> WSO2 Inc. http://wso2.com ,
>>>> Mobile: (+94) 714 115 032
>>>>
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Dushan Abeyruwan | Associate Tech Lead
>>>  Integration Technologies Team
>>> PMC Member Apache Synpase
>>> WSO2 Inc. http://wso2.com/
>>> Blog:http://dushansview.blogspot.com/
>>> Mobile:(0094)713942042
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Milinda Perera
>> Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to