Adding more. Since we will follow the whiteboard pattern for adding new MembershipListener's, we don't need to have the methods ( *addMembershipListener, **addMembershipListener*) explicitly at API level. Users will implement their MembershipListener's and register it as an OSGi service. The clustering component will discover these and add it the cluster impl.
On Wed, Jan 15, 2014 at 3:03 PM, Afkham Azeez <[email protected]> wrote: > Anjana & Suho, > Please review this & let us know whether these APIs address your > requirements. > > Azeez > > > On Wed, Jan 15, 2014 at 1:40 PM, Kishanthan Thangarajah < > [email protected]> wrote: > >> This thread is to discuss about $subject. >> >> Our current clustering API's contains stuffs that are mixture of both >> user level and developer level API. We will have to separate out these with >> the clear definition. >> >> For clustering API (user level), we will have the following methods. We >> can discuss clustering SPI's on a separate thread. >> >> * void sendMessage(ClusterMessage clusterMessage);* >> >> * void sendMessage(ClusterMessage clusterMessage, List<ClusterMember> >> members);* >> >> * List<ClusterMember> getMembers();* >> >> * void addMembershipListener(MembershipListener membershipListener);* >> >> * void removeMembershipListener(MembershipListener >> membershipListener);* >> >> In here we also thought of having MembershipListener (A listener which >> gets notified when changes occur in Membership) related API at user level. >> This will be useful when user wants to get some event notification when the >> current membership changes. Adding a new MembershipListener will follow the >> white board pattern. >> >> The API for MembershipListener >> >> * void memberAdded(MembershipEvent event);* >> >> * void memberRemoved(MembershipEvent event);* >> >> MembershipEvent will be of two types (member added or removed). >> >> Thoughts? >> >> Thanks, >> Kishanthan. >> -- >> *Kishanthan Thangarajah* >> Senior Software Engineer, >> Platform Technologies Team, >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - +94773426635 >> Blog - *http://kishanthan.wordpress.com >> <http://kishanthan.wordpress.com>* >> Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* >> > > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>* > *email: **[email protected]* <[email protected]> > * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * > *http://blog.afkham.org* <http://blog.afkham.org> > *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* > -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
