Re: [Architecture] ESB Connector | SoundCloud

2014-06-19 Thread Gagani Amarathunga
Looping in Samisa.

Please find the google doc link for the project plan.

https://docs.google.com/spreadsheets/d/1SfJr59gHK-UGyjN7QCwCspZ0lYv8abws_RX_pK5WOso/edit?usp=sharing

Thank you.

Gagani Amarathunga


On Tue, Jun 17, 2014 at 3:11 PM, Gagani Amarathunga <
gagani.amarathu...@gmail.com> wrote:

> Hi,
>
> Could you please review the project plan and its possibility to us.
>
> Thank you.
> Gagani Amarathunga
>
>
>
> On Tue, Jun 17, 2014 at 9:43 AM, Gagani Amarathunga <
> gagani.amarathu...@gmail.com> wrote:
>
>> Hi Malaka,
>>
>> Yes, we have covered everything.
>>
>> Best Regards,
>> Gagani Amarathunga
>>
>>
>> On Tue, Jun 17, 2014 at 6:44 AM, Malaka Silva  wrote:
>>
>>> Hi Gagani,
>>>
>>> This looks good. I guess you have covered almost everything?
>>>
>>> Best Regards,
>>> Malaka
>>>
>>>
>>> On Mon, Jun 16, 2014 at 2:21 AM, Gagani Amarathunga <
>>> gagani.amarathu...@gmail.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We have reviewed the functions for the API based on its current
>>>> availability. Could anyone please be kind enough to review the soundcloud
>>>> connector details.
>>>>
>>>>
>>>>
>>>> *Introduction*
>>>>
>>>> SoundCloud is an audio platform that enables sound creators to upload,
>>>> record, promote and share their originally-created sounds.In SoundCloud we
>>>> can follow favorite artists, labels and friends and see every track they
>>>> post.
>>>>
>>>> The SoundCloud API exposes SoundCloud resources like sounds, sets and
>>>> users. These resources can be accessed and manipulated using the HTTP
>>>> methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to
>>>> maintain information about users, tracks, playlists, sounds, sets,etc.
>>>>
>>>>
>>>> *SoundCloud Connector Summary*
>>>>
>>>> • Connector Name:  souncloud-connector-1.0.0
>>>> • Version: 1.0.0
>>>> • Technology:  REST
>>>>
>>>>
>>>> *Authentication*
>>>>
>>>> SoundCloud API uses OAuth2 based authentication
>>>>
>>>>
>>>> *Selected API Methods*
>>>>
>>>> *users*
>>>> get user
>>>> list of tracks of the user
>>>> list of playlists (sets) of the user
>>>> list of users who are followed by the user
>>>> list of users who are following the user
>>>> list of comments from this user
>>>> list of tracks favorited by the user
>>>> list of joined groups
>>>> list of web profiles
>>>>
>>>> *tracks*
>>>> get a track
>>>> comments for the track
>>>> a comment for the track
>>>> users who favorited the track
>>>>
>>>> *playlists* - A SoundCloud Set is internally called playlists due to
>>>> some naming restrictions.
>>>> get a playlist
>>>>
>>>> *groups* - Groups have members and contributed tracks.
>>>> get a group
>>>> list of users who moderate the group
>>>> list of users who joined the group
>>>> list of users who contributed a track to the group
>>>> list of users who contributed to, joined or moderate the group
>>>> list of contributed and approved tracks
>>>>
>>>> *comments* - Comments can be made on tracks by any user who has access
>>>> to a track.
>>>>
>>>> *me* -  Get information about the authenticated user and easily access
>>>> related subresources like tracks, followings, followers, groups.
>>>>  get self information
>>>>
>>>>
>>>> *connections* - Connections represent the external profiles (like
>>>> twitter, tumblr or facebook profiles and pages) that are connected to a
>>>> SoundCloud user.
>>>>
>>>> *activities* - The newest activities for the logged-in user.
>>>>
>>>> *apps* - All tracks that are created and uploaded using a published
>>>> app.
>>>>
>>>> *resolve* - The resolve resource allows to lookup and access API
>>>> resources when only know the SoundCloud.com URL.
>>>>
>>>> *oembed* - oEmbed is a

Re: [Architecture] ESB Connector | SoundCloud

2014-06-17 Thread Gagani Amarathunga
Hi,

Could you please review the project plan and its possibility to us.

Thank you.
Gagani Amarathunga



On Tue, Jun 17, 2014 at 9:43 AM, Gagani Amarathunga <
gagani.amarathu...@gmail.com> wrote:

> Hi Malaka,
>
> Yes, we have covered everything.
>
> Best Regards,
> Gagani Amarathunga
>
>
> On Tue, Jun 17, 2014 at 6:44 AM, Malaka Silva  wrote:
>
>> Hi Gagani,
>>
>> This looks good. I guess you have covered almost everything?
>>
>> Best Regards,
>> Malaka
>>
>>
>> On Mon, Jun 16, 2014 at 2:21 AM, Gagani Amarathunga <
>> gagani.amarathu...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We have reviewed the functions for the API based on its current
>>> availability. Could anyone please be kind enough to review the soundcloud
>>> connector details.
>>>
>>>
>>>
>>> *Introduction*
>>>
>>> SoundCloud is an audio platform that enables sound creators to upload,
>>> record, promote and share their originally-created sounds.In SoundCloud we
>>> can follow favorite artists, labels and friends and see every track they
>>> post.
>>>
>>> The SoundCloud API exposes SoundCloud resources like sounds, sets and
>>> users. These resources can be accessed and manipulated using the HTTP
>>> methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to
>>> maintain information about users, tracks, playlists, sounds, sets,etc.
>>>
>>>
>>> *SoundCloud Connector Summary*
>>>
>>> • Connector Name:  souncloud-connector-1.0.0
>>> • Version: 1.0.0
>>> • Technology:  REST
>>>
>>>
>>> *Authentication*
>>>
>>> SoundCloud API uses OAuth2 based authentication
>>>
>>>
>>> *Selected API Methods*
>>>
>>> *users*
>>> get user
>>> list of tracks of the user
>>> list of playlists (sets) of the user
>>> list of users who are followed by the user
>>> list of users who are following the user
>>> list of comments from this user
>>> list of tracks favorited by the user
>>> list of joined groups
>>> list of web profiles
>>>
>>> *tracks*
>>> get a track
>>> comments for the track
>>> a comment for the track
>>> users who favorited the track
>>>
>>> *playlists* - A SoundCloud Set is internally called playlists due to
>>> some naming restrictions.
>>> get a playlist
>>>
>>> *groups* - Groups have members and contributed tracks.
>>> get a group
>>> list of users who moderate the group
>>> list of users who joined the group
>>> list of users who contributed a track to the group
>>> list of users who contributed to, joined or moderate the group
>>> list of contributed and approved tracks
>>>
>>> *comments* - Comments can be made on tracks by any user who has access
>>> to a track.
>>>
>>> *me* -  Get information about the authenticated user and easily access
>>> related subresources like tracks, followings, followers, groups.
>>>  get self information
>>>
>>>
>>> *connections* - Connections represent the external profiles (like
>>> twitter, tumblr or facebook profiles and pages) that are connected to a
>>> SoundCloud user.
>>>
>>> *activities* - The newest activities for the logged-in user.
>>>
>>> *apps* - All tracks that are created and uploaded using a published app.
>>>
>>> *resolve* - The resolve resource allows to lookup and access API
>>> resources when only know the SoundCloud.com URL.
>>>
>>> *oembed* - oEmbed is an open standard to easily embed content from
>>> oEmbed providers into the site.
>>>
>>>
>>> Above are the methods that is going to be implemented in the soundcloud
>>> connector. We have taken all the methods that are supported by the current
>>> soundclound API.[1]
>>>
>>> [1]http://developers.soundcloud.com/docs/api/reference
>>>  [2]http://developers.soundcloud.com/console
>>>
>>> Thank you.
>>>
>>>
>>>
>>> On Fri, Jun 13, 2014 at 3:08 PM, Gagani Amarathunga <
>>> gagani.amarathu...@gmail.com> wrote:
>>>
>>>> Looping in Malaka, Dushan, Shevan
>>>>
>>>>
>>>> On Fri, Jun 13, 2014 at 11:42 AM, Ga

Re: [Architecture] ESB Connector | SoundCloud

2014-06-16 Thread Gagani Amarathunga
Hi Malaka,

Yes, we have covered everything.

Best Regards,
Gagani Amarathunga


On Tue, Jun 17, 2014 at 6:44 AM, Malaka Silva  wrote:

> Hi Gagani,
>
> This looks good. I guess you have covered almost everything?
>
> Best Regards,
> Malaka
>
>
> On Mon, Jun 16, 2014 at 2:21 AM, Gagani Amarathunga <
> gagani.amarathu...@gmail.com> wrote:
>
>> Hi All,
>>
>> We have reviewed the functions for the API based on its current
>> availability. Could anyone please be kind enough to review the soundcloud
>> connector details.
>>
>>
>>
>> *Introduction*
>>
>> SoundCloud is an audio platform that enables sound creators to upload,
>> record, promote and share their originally-created sounds.In SoundCloud we
>> can follow favorite artists, labels and friends and see every track they
>> post.
>>
>> The SoundCloud API exposes SoundCloud resources like sounds, sets and
>> users. These resources can be accessed and manipulated using the HTTP
>> methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to
>> maintain information about users, tracks, playlists, sounds, sets,etc.
>>
>>
>> *SoundCloud Connector Summary*
>>
>> • Connector Name:  souncloud-connector-1.0.0
>> • Version: 1.0.0
>> • Technology:  REST
>>
>>
>> *Authentication*
>>
>> SoundCloud API uses OAuth2 based authentication
>>
>>
>> *Selected API Methods*
>>
>> *users*
>> get user
>> list of tracks of the user
>> list of playlists (sets) of the user
>> list of users who are followed by the user
>> list of users who are following the user
>> list of comments from this user
>> list of tracks favorited by the user
>> list of joined groups
>> list of web profiles
>>
>> *tracks*
>> get a track
>> comments for the track
>> a comment for the track
>> users who favorited the track
>>
>> *playlists* - A SoundCloud Set is internally called playlists due to
>> some naming restrictions.
>> get a playlist
>>
>> *groups* - Groups have members and contributed tracks.
>> get a group
>> list of users who moderate the group
>> list of users who joined the group
>> list of users who contributed a track to the group
>> list of users who contributed to, joined or moderate the group
>> list of contributed and approved tracks
>>
>> *comments* - Comments can be made on tracks by any user who has access
>> to a track.
>>
>> *me* -  Get information about the authenticated user and easily access
>> related subresources like tracks, followings, followers, groups.
>>  get self information
>>
>>
>> *connections* - Connections represent the external profiles (like
>> twitter, tumblr or facebook profiles and pages) that are connected to a
>> SoundCloud user.
>>
>> *activities* - The newest activities for the logged-in user.
>>
>> *apps* - All tracks that are created and uploaded using a published app.
>>
>> *resolve* - The resolve resource allows to lookup and access API
>> resources when only know the SoundCloud.com URL.
>>
>> *oembed* - oEmbed is an open standard to easily embed content from
>> oEmbed providers into the site.
>>
>>
>> Above are the methods that is going to be implemented in the soundcloud
>> connector. We have taken all the methods that are supported by the current
>> soundclound API.[1]
>>
>> [1]http://developers.soundcloud.com/docs/api/reference
>>  [2]http://developers.soundcloud.com/console
>>
>> Thank you.
>>
>>
>>
>> On Fri, Jun 13, 2014 at 3:08 PM, Gagani Amarathunga <
>> gagani.amarathu...@gmail.com> wrote:
>>
>>> Looping in Malaka, Dushan, Shevan
>>>
>>>
>>> On Fri, Jun 13, 2014 at 11:42 AM, Gagani Amarathunga <
>>> gagani.amarathu...@gmail.com> wrote:
>>>
>>>> *Introduction*
>>>>
>>>> SoundCloud is an audio platform that enables sound creators to upload,
>>>> record, promote and share their originally-created sounds.In SoundCloud we
>>>> can follow favorite artists, labels and friends and see every track they
>>>> post.
>>>>
>>>> The SoundCloud API exposes SoundCloud resources like sounds, sets and
>>>> users. These resources can be accessed and manipulated using the HTTP
>>>> methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to

Re: [Architecture] ESB Connector | SoundCloud

2014-06-15 Thread Gagani Amarathunga
Hi All,

We have reviewed the functions for the API based on its current
availability. Could anyone please be kind enough to review the soundcloud
connector details.


*Introduction*

SoundCloud is an audio platform that enables sound creators to upload,
record, promote and share their originally-created sounds.In SoundCloud we
can follow favorite artists, labels and friends and see every track they
post.

The SoundCloud API exposes SoundCloud resources like sounds, sets and
users. These resources can be accessed and manipulated using the HTTP
methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to
maintain information about users, tracks, playlists, sounds, sets,etc.


*SoundCloud Connector Summary*

• Connector Name:  souncloud-connector-1.0.0
• Version: 1.0.0
• Technology:  REST


*Authentication*

SoundCloud API uses OAuth2 based authentication


*Selected API Methods*

*users*
get user
list of tracks of the user
list of playlists (sets) of the user
list of users who are followed by the user
list of users who are following the user
list of comments from this user
list of tracks favorited by the user
list of joined groups
list of web profiles

*tracks*
get a track
comments for the track
a comment for the track
users who favorited the track

*playlists* - A SoundCloud Set is internally called playlists due to some
naming restrictions.
get a playlist

*groups* - Groups have members and contributed tracks.
get a group
list of users who moderate the group
list of users who joined the group
list of users who contributed a track to the group
list of users who contributed to, joined or moderate the group
list of contributed and approved tracks

*comments* - Comments can be made on tracks by any user who has access to a
track.

*me* -  Get information about the authenticated user and easily access
related subresources like tracks, followings, followers, groups.
get self information

*connections* - Connections represent the external profiles (like twitter,
tumblr or facebook profiles and pages) that are connected to a SoundCloud
user.

*activities* - The newest activities for the logged-in user.

*apps* - All tracks that are created and uploaded using a published app.

*resolve* - The resolve resource allows to lookup and access API resources
when only know the SoundCloud.com URL.

*oembed* - oEmbed is an open standard to easily embed content from oEmbed
providers into the site.


Above are the methods that is going to be implemented in the soundcloud
connector. We have taken all the methods that are supported by the current
soundclound API.[1]

[1]http://developers.soundcloud.com/docs/api/reference
[2]http://developers.soundcloud.com/console

Thank you.



On Fri, Jun 13, 2014 at 3:08 PM, Gagani Amarathunga <
gagani.amarathu...@gmail.com> wrote:

> Looping in Malaka, Dushan, Shevan
>
>
> On Fri, Jun 13, 2014 at 11:42 AM, Gagani Amarathunga <
> gagani.amarathu...@gmail.com> wrote:
>
>> *Introduction*
>>
>> SoundCloud is an audio platform that enables sound creators to upload,
>> record, promote and share their originally-created sounds.In SoundCloud we
>> can follow favorite artists, labels and friends and see every track they
>> post.
>>
>> The SoundCloud API exposes SoundCloud resources like sounds, sets and
>> users. These resources can be accessed and manipulated using the HTTP
>> methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to
>> maintain information about users, tracks, playlists, sounds, sets,etc.
>>
>>
>> *SoundCloud Connector Summary*
>>
>> • Connector Name:  souncloud-connector-1.0.0
>> • Version: 1.0.0
>> • Technology:  REST
>>
>>
>> *Authentication*
>>
>> SoundCloud API uses OAuth2 based authentication
>>
>>
>> *Selected API Methods*
>>
>> *users*
>> get user
>> list of tracks of the user
>> list of playlists (sets) of the user
>> list of users who are followed by the user
>> a user who is followed by the user
>> list of users who are following the user
>> user who is following the user
>> list of comments from this user
>> list of tracks favorited by the user
>> track favorited by the user
>> list of joined groups
>> list of web profiles
>>
>> *tracks*
>> get a track
>> comments for the track
>> a comment for the track
>> users who favorited the track
>> a user who has favorited to the track
>> users who have access to the track
>> email addresses who are invited to the track
>> secret token of the track
>>
>>
>> *playlists* - A SoundCloud S

Re: [Architecture] ESB Connector | SoundCloud

2014-06-13 Thread Gagani Amarathunga
Looping in Malaka, Dushan, Shevan


On Fri, Jun 13, 2014 at 11:42 AM, Gagani Amarathunga <
gagani.amarathu...@gmail.com> wrote:

> *Introduction*
>
> SoundCloud is an audio platform that enables sound creators to upload,
> record, promote and share their originally-created sounds.In SoundCloud we
> can follow favorite artists, labels and friends and see every track they
> post.
>
> The SoundCloud API exposes SoundCloud resources like sounds, sets and
> users. These resources can be accessed and manipulated using the HTTP
> methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to
> maintain information about users, tracks, playlists, sounds, sets,etc.
>
>
> *SoundCloud Connector Summary*
>
> • Connector Name:  souncloud-connector-1.0.0
> • Version: 1.0.0
> • Technology:  REST
>
>
> *Authentication*
>
> SoundCloud API uses OAuth2 based authentication
>
>
> *Selected API Methods*
>
> *users*
> get user
> list of tracks of the user
> list of playlists (sets) of the user
> list of users who are followed by the user
> a user who is followed by the user
> list of users who are following the user
> user who is following the user
> list of comments from this user
> list of tracks favorited by the user
> track favorited by the user
> list of joined groups
> list of web profiles
>
> *tracks*
> get a track
> comments for the track
> a comment for the track
> users who favorited the track
> a user who has favorited to the track
> users who have access to the track
> email addresses who are invited to the track
> secret token of the track
>
>
> *playlists* - A SoundCloud Set is internally called playlists due to some
> naming restrictions.
> get a playlist
> users who have access to the track
> email addresses who are invited to the playlist
> secret token of the playlist
>
> *groups* - Groups have members and contributed tracks.
> get a group
> list of users who moderate the group
> list of users who joined the group
> list of users who contributed a track to the group
> list of users who contributed to, joined or moderate the group
> list of contributed and approved tracks
> list of contributed but not approved tracks (for moderators)
> a contributed but not approved track (for moderators)
> list of contributed tracks (for moderators). POST creates contribution
> a contributed track (for moderators)
>
> *comments* - Comments can be made on tracks by any user who has access to
> a track.
>
> *me* -  Get information about the authenticated user and easily access
> related subresources like tracks, followings, followers, groups.
> get authenticated user
> list of tracks of the user
> list of playlists (sets) of the user
> list of users who are followed by the user
> a user who is followed by the user
> list of users who are following the user
> user who is following the user
> list of comments from this user
> list of tracks favorited by the user
> track favorited by the user
> list of joined groups
> list of web profiles
> list dashboard activities
> list of connected external profiles
>
> *connections* - Connections represent the external profiles (like
> twitter, tumblr or facebook profiles and pages) that are connected to a
> SoundCloud user.
>
> *activities* - The newest activities for the logged-in user.
>
> *apps* - All tracks that are created and uploaded using a published app.
>
> *resolve* - The resolve resource allows to lookup and access API
> resources when only know the SoundCloud.com URL.
>
> *oembed* - oEmbed is an open standard to easily embed content from oEmbed
> providers into the site.
>
>
> Above are the methods that is going to be implemented in the soundcloud
> connector. We have taken all the methods that are supported by the current
> soundclound API.[1]
>
> [1]http://developers.soundcloud.com/docs/api/reference
>
> Please let us know the feedback on the above.
>
> Thank you.
> Gagani Amarathunga
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


[Architecture] ESB Connector | SoundCloud

2014-06-12 Thread Gagani Amarathunga
*Introduction*

SoundCloud is an audio platform that enables sound creators to upload,
record, promote and share their originally-created sounds.In SoundCloud we
can follow favorite artists, labels and friends and see every track they
post.

The SoundCloud API exposes SoundCloud resources like sounds, sets and
users. These resources can be accessed and manipulated using the HTTP
methods GET, POST, PUT and DELETE. Basically SoundCloud API supports us to
maintain information about users, tracks, playlists, sounds, sets,etc.


*SoundCloud Connector Summary*

• Connector Name:  souncloud-connector-1.0.0
• Version: 1.0.0
• Technology:  REST


*Authentication*

SoundCloud API uses OAuth2 based authentication


*Selected API Methods*

*users*
get user
list of tracks of the user
list of playlists (sets) of the user
list of users who are followed by the user
a user who is followed by the user
list of users who are following the user
user who is following the user
list of comments from this user
list of tracks favorited by the user
track favorited by the user
list of joined groups
list of web profiles

*tracks*
get a track
comments for the track
a comment for the track
users who favorited the track
a user who has favorited to the track
users who have access to the track
email addresses who are invited to the track
secret token of the track


*playlists* - A SoundCloud Set is internally called playlists due to some
naming restrictions.
get a playlist
users who have access to the track
email addresses who are invited to the playlist
secret token of the playlist

*groups* - Groups have members and contributed tracks.
get a group
list of users who moderate the group
list of users who joined the group
list of users who contributed a track to the group
list of users who contributed to, joined or moderate the group
list of contributed and approved tracks
list of contributed but not approved tracks (for moderators)
a contributed but not approved track (for moderators)
list of contributed tracks (for moderators). POST creates contribution
a contributed track (for moderators)

*comments* - Comments can be made on tracks by any user who has access to a
track.

*me* -  Get information about the authenticated user and easily access
related subresources like tracks, followings, followers, groups.
get authenticated user
list of tracks of the user
list of playlists (sets) of the user
list of users who are followed by the user
a user who is followed by the user
list of users who are following the user
user who is following the user
list of comments from this user
list of tracks favorited by the user
track favorited by the user
list of joined groups
list of web profiles
list dashboard activities
list of connected external profiles

*connections* - Connections represent the external profiles (like twitter,
tumblr or facebook profiles and pages) that are connected to a SoundCloud
user.

*activities* - The newest activities for the logged-in user.

*apps* - All tracks that are created and uploaded using a published app.

*resolve* - The resolve resource allows to lookup and access API resources
when only know the SoundCloud.com URL.

*oembed* - oEmbed is an open standard to easily embed content from oEmbed
providers into the site.


Above are the methods that is going to be implemented in the soundcloud
connector. We have taken all the methods that are supported by the current
soundclound API.[1]

[1]http://developers.soundcloud.com/docs/api/reference

Please let us know the feedback on the above.

Thank you.
Gagani Amarathunga
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture