Hi Manil, Do you plan to progress this further?
Thanks Shevan On Tue, Sep 16, 2014 at 4:36 PM, Manil Liyanage <[email protected]> wrote: > Hi Vanji, > > We dont have a much progress from the last place we stopped. But we are > working on it now and we will be finishing it soon. > > Thanks, > Manil > > On Tue, Sep 2, 2014 at 1:26 PM, Vanjikumaran Sivajothy <[email protected]> > wrote: > >> Hi Manil, >> Is there any update on your connector project progress? >> >> Best Regards, >> Vanji >> >> >> On Fri, Jul 18, 2014 at 10:53 AM, Ramindu Deshapriya <[email protected]> >> wrote: >> >>> Hi Lasantha, >>> >>> Your point is correct, the decision needs to be made whether we would >>> actually need to send an old message via email later on. >>> >>> Thanks. >>> >>> >>> On Thu, Jul 17, 2014 at 8:01 AM, Lasantha Fernando <[email protected]> >>> wrote: >>> >>>> Hi Ramindu, >>>> >>>> I haven't gone through the API deeply. But isn't emailing messages >>>> method there to email any message to the user, not just newly created ones? >>>> I mean, would a user be able to email any received message by invoking the >>>> 'Emailing messages' endpoint? If so, chaining the two methods together >>>> might mean a loss functionality for the user. >>>> >>>> I might have understood the API incorrectly, and if so please correct >>>> me... :-). >>>> >>>> Thanks, >>>> Lasantha >>>> >>>> >>>> On 16 July 2014 16:23, Ramindu Deshapriya <[email protected]> wrote: >>>> >>>>> Hi Manil, >>>>> >>>>> Looks like you're giving good coverage to all methods. That's great. >>>>> >>>>> I think you'd be able to cover the Emailing messages method when >>>>> creating a message (specify whether or not to send the message as an >>>>> email). I know it needs another API call, but you could chain them >>>>> together >>>>> to provide more easy-to-use functionality for the client. >>>>> >>>>> Vanjikumaran, the attachments api provides the ability to create a >>>>> pending attachment, for which you will be given an ID which can then be >>>>> attached to an individual message, thread etc. >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> On Wed, Jul 16, 2014 at 3:49 PM, Vanjikumaran Sivajothy < >>>>> [email protected]> wrote: >>>>> >>>>>> I am not clear with the attachments API, Please do some more reading >>>>>> on that. >>>>>> >>>>>> Send your project plan with the detail work breakdown. Rest of them >>>>>> are looking good. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jul 16, 2014 at 12:18 PM, Manil Liyanage < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> *Introduction* >>>>>>> >>>>>>> Yammer is a private social network that helps employees collaborate >>>>>>> across departments, locations and business apps. The Yammer API is a >>>>>>> rest >>>>>>> based one. It has GET, POST, PUT and DELETE methods. >>>>>>> >>>>>>> *Yammer Connector Summary* >>>>>>> >>>>>>> • Connector Name: yammer-connector-1.0.0 >>>>>>> • Version: 1.0.0 >>>>>>> • Technology: REST >>>>>>> >>>>>>> >>>>>>> *Authentication* >>>>>>> >>>>>>> Yammer API uses OAuth2 based authentication >>>>>>> >>>>>>> >>>>>>> *Selected API Methods* >>>>>>> >>>>>>> *Messages* >>>>>>> Public messages >>>>>>> Feed >>>>>>> Algorithmic feed >>>>>>> Following >>>>>>> Sent >>>>>>> Private >>>>>>> Received >>>>>>> Create a new message >>>>>>> Remove a message >>>>>>> >>>>>>> *Pending Attachments* >>>>>>> Create >>>>>>> Delete >>>>>>> >>>>>>> *Emailing Messages* >>>>>>> Emailing Messages method >>>>>>> >>>>>>> >>>>>>> *Viewing Threads*Viewing Threads method >>>>>>> >>>>>>> >>>>>>> *Emailing* >>>>>>> Emailing method >>>>>>> >>>>>>> >>>>>>> *Likes* >>>>>>> Post a like >>>>>>> Remove a like >>>>>>> >>>>>>> >>>>>>> *Topics*Get by ID >>>>>>> Get by Hashtag >>>>>>> >>>>>>> >>>>>>> *Groups* >>>>>>> Join >>>>>>> Leave >>>>>>> >>>>>>> *Users* >>>>>>> Users in current users network >>>>>>> About current user >>>>>>> About a user >>>>>>> By Alias >>>>>>> Users in a group >>>>>>> >>>>>>> *Relationships* >>>>>>> Show >>>>>>> Add >>>>>>> Remove >>>>>>> >>>>>>> >>>>>>> *Notifications* >>>>>>> Notifications method >>>>>>> >>>>>>> >>>>>>> *Suggestions *Show >>>>>>> Decline >>>>>>> >>>>>>> >>>>>>> *Subscriptions* >>>>>>> Check for user >>>>>>> Check for thread >>>>>>> Check for topic >>>>>>> Subscribe to topic >>>>>>> Unsubscribe to topic >>>>>>> >>>>>>> *Autocomplete* >>>>>>> Autocomplete method >>>>>>> >>>>>>> >>>>>>> *Invitations*Invitations method >>>>>>> >>>>>>> >>>>>>> *Search * >>>>>>> Search method >>>>>>> >>>>>>> *Network* >>>>>>> Network Method >>>>>>> >>>>>>> Above are the methods that is going to be implemented in the yammer >>>>>>> connector. We have taken all the methods that are supported by the >>>>>>> current >>>>>>> yammer API except add, update and suspend user due to its a paid user's >>>>>>> functionality.[1] >>>>>>> >>>>>>> [1]https://developer.yammer.com/restapi/ >>>>>>> <http://developers.soundcloud.com/docs/api/reference> >>>>>>> >>>>>>> Please let us know the feedback on the above. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sivajothy Vanjikumaran >>>>>> *Senior Software Engineer* >>>>>> *Integration Technologies Team* >>>>>> *WSO2 Inc. http://wso2.com <http://wso2.com/>* >>>>>> *Mobile:(+94)777219209* >>>>>> [image: Facebook] <https://www.facebook.com/vanjikumaran> [image: >>>>>> Twitter] <https://twitter.com/vanjikumaran> [image: LinkedIn] >>>>>> <http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> [image: >>>>>> Blogger] <http://vanjikumaran.blogspot.com/> [image: SlideShare] >>>>>> <http://www.slideshare.net/vanjikumaran> >>>>>> >>>>>> This communication may contain privileged or other >>>>>> confidential information and is intended exclusively for the addressee/s. >>>>>> If you are not the intended recipient/s, or believe that you may >>>>>> have received this communication in error, please reply to the >>>>>> sender indicating that fact and delete the copy you received and in >>>>>> addition, you should not print, copy, re-transmit, disseminate, or >>>>>> otherwise use the information contained in this communication. >>>>>> Internet communications cannot be guaranteed to be timely, secure, error >>>>>> or virus-free. The sender does not accept liability for any errors >>>>>> or omissions >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Au revoir! >>>>> Ramindu Deshapriya. >>>>> >>>>> Member - Sahana Software Foundation http://sahanafoundation.org >>>>> http://rdeshapriya.com >>>>> >>>>> <http://www.facebook.com/rdeshapriya> >>>>> <http://twitter.com/#%21/rami_desh> >>>>> <https://plus.google.com/113801459480978566130> >>>>> <http://www.linkedin.com/profile/view?id=84017607&trk=tab_pro> >>>>> <http://rdeshapriya.com> <http://lmakuthan.blogspot.com> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Lasantha Fernando* >>>> Software Engineer - Data Technologies Team >>>> WSO2 Inc. http://wso2.com >>>> >>>> email: [email protected] >>>> mobile: (+94) 71 5247551 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Au revoir! >>> Ramindu Deshapriya. >>> >>> Member - Sahana Software Foundation http://sahanafoundation.org >>> http://rdeshapriya.com >>> >>> <http://www.facebook.com/rdeshapriya> >>> <http://twitter.com/#%21/rami_desh> >>> <https://plus.google.com/113801459480978566130> >>> <http://www.linkedin.com/profile/view?id=84017607&trk=tab_pro> >>> <http://rdeshapriya.com> <http://lmakuthan.blogspot.com> >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Sivajothy Vanjikumaran >> *Senior Software Engineer* >> *Integration Technologies Team* >> *WSO2 Inc. http://wso2.com <http://wso2.com/>* >> *Mobile:(+94)777219209* >> [image: Facebook] <https://www.facebook.com/vanjikumaran> [image: >> Twitter] <https://twitter.com/vanjikumaran> [image: LinkedIn] >> <http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> [image: >> Blogger] <http://vanjikumaran.blogspot.com/> [image: SlideShare] >> <http://www.slideshare.net/vanjikumaran> >> >> This communication may contain privileged or other >> confidential information and is intended exclusively for the addressee/s. >> If you are not the intended recipient/s, or believe that you may >> have received this communication in error, please reply to the >> sender indicating that fact and delete the copy you received and in >> addition, you should not print, copy, re-transmit, disseminate, or >> otherwise use the information contained in this communication. >> Internet communications cannot be guaranteed to be timely, secure, error >> or virus-free. The sender does not accept liability for any errors >> or omissions >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
