Hi Samisa,
On Tue, Jul 30, 2013 at 10:25 AM, Samisa Abeysinghe <[email protected]> wrote: > I am not really clear how the "group" around an AF project team will be > handled with users and roles. > > Anyway, lets have an initial implementation so that we have some ground to > review rather than ague theoretically. > +1, that's our plan too. we will do the initial implementation based on what we have right now, considering basic usecase, and then improve based on that. > > Also, for the sake of "analysis" and "intelligence" is there a way to > re-use BAM models for tracking comments? Given that we are going to use big > data for storage anyway. > Yes, we will be storing the comments/rating/other events in BAM storage, hence, we can define required analytic. Regards, /Nuwan > > > On Mon, Jul 29, 2013 at 11:37 AM, Srinath Perera <[email protected]> wrote: > >> Hi Manu, >> >> Key is when you store data, always keep the root activity ID as well so >> we can retrieve the all comments related to this activity from Cassandra >> without walking the tree to get all the levels. First one is a one query >> while walking the tree can be 100s of queries. >> >> We can do this by having a correlationID and parent ID separately >> activities and always setting rootID as the correlation ID. >> >> --Srinath >> >> >> >> On Mon, Jul 29, 2013 at 9:45 AM, Manuranga Perera <[email protected]> wrote: >> >>> at code level we are planing to support multiple levels because it will >>> be useful in the feature to extend it to a more forum like look. but the >>> host application will be able to pass a parameter to limit it to single >>> level. >>> For store use case we are having single (or double , haven’t finalized >>> yet) level commenting. >>> >>> >>> On Mon, Jul 29, 2013 at 8:39 AM, Sameera Perera <[email protected]>wrote: >>> >>>> Hi Manu, >>>> >>>> One question regarding the "Comment on Comment" use case. >>>> How deep of a nesting are you planning to support? Multiple levles (as >>>> in CodeProject) or just a single level below the initial comment? >>>> >>>> >>>> On Sun, Jul 28, 2013 at 12:00 AM, Manuranga Perera <[email protected]>wrote: >>>> >>>>> As the first step of implementing social features for WOS2 products we >>>>> are planning to implement a commenting system. It will be integrated to >>>>> store first and subsequently to the AF. Italicized terms are used in the >>>>> meaning as it’s defined by the Activity Stream specification [0]. A PoC >>>>> will be done based on the architecture described below, and we shall >>>>> re-review this architecture after that. >>>>> * >>>>> Implementation details* >>>>> >>>>> >>>>> - Each input will be an activity including comments and ratings. >>>>> this will be extendible to receive activities form the host application >>>>> (i.e. WSO2 ES/AF) as well as from third party systems (such as JIRA). >>>>> - Cassandra will be used as the database. this will allow us to >>>>> plug-in BAM and CEP for analyzing and event generation later-on. we >>>>> will >>>>> reuse the BAM’s Event Stream architecture to store data. but we will >>>>> try to >>>>> retrieve data (at least most of it) directly via CQL interface rather >>>>> than >>>>> going through HIVE to avoid update delays. >>>>> - UI will be a separate Jaggery app, and it will be integrated to >>>>> the host application UI via a HTML IFrame. UI will be SSOed with the >>>>> host >>>>> application. >>>>> - Permission will be handled using existing carbon user role >>>>> system. we plan to be aligned with AF’s future model, since we should >>>>> be >>>>> able to use AF’s team concept.To do this, we define a UI-visible sub >>>>> set >>>>> of user’s roles. each action of the user will be published against one >>>>> of >>>>> these roles. any action published to a role will be visible to all the >>>>> users in that role. >>>>> - A REST API will be available for publishing activities to roles. >>>>> >>>>> * >>>>> Use-cases to be implemented in first release (with Store 1.0 and AF >>>>> APasS)* >>>>> >>>>> >>>>> - View >>>>> - View commnet stream for an object. an object can be a Store >>>>> asset, API, AF application, etc. >>>>> - View my activity stream - this will show all activities that >>>>> are visible for me including relevant comments. >>>>> >>>>> >>>>> - Comment >>>>> - Comment on an object >>>>> - Comment on comments >>>>> - Rate >>>>> - Rate objects >>>>> - Rate comments >>>>> >>>>> * >>>>> Possible future use-cases* >>>>> >>>>> - Real time updating the UI when events occur >>>>> - Extend the same back-end to a forum >>>>> - Integrate with a platform wide friend/circles concept >>>>> >>>>> [0] http://activitystrea.ms/specs/json/1.0/ >>>>> >>>>> -- >>>>> With regards, >>>>> *Manu*ranga Perera. >>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> ------------------------------ >>>> >>>> *Sameera Perera* >>>> Senior Manager, Cloud Technology Group >>>> gtalk: [email protected] >>>> *WSO2, Inc.* <http://wso2.com/> >>>> lean.enterprise.middleware >>>> >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> With regards, >>> *Manu*ranga Perera. >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> http://people.apache.org/~hemapani/ >> http://srinathsview.blogspot.com/ >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Thanks & Regards, Nuwan Bandara Technical Lead; **WSO2 Inc. * *lean . enterprise . middleware | http://wso2.com * *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
