Return-Path: X-Original-To: apmail-stratos-dev-archive@minotaur.apache.org Delivered-To: apmail-stratos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D3A41109DC for ; Sat, 4 Jan 2014 15:28:38 +0000 (UTC) Received: (qmail 91274 invoked by uid 500); 4 Jan 2014 15:28:33 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 91247 invoked by uid 500); 4 Jan 2014 15:28:30 -0000 Mailing-List: contact dev-help@stratos.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stratos.incubator.apache.org Delivered-To: mailing list dev@stratos.incubator.apache.org Received: (qmail 91237 invoked by uid 99); 4 Jan 2014 15:28:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jan 2014 15:28:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lahirus@wso2.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qc0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jan 2014 15:28:20 +0000 Received: by mail-qc0-f171.google.com with SMTP id c9so15703763qcz.16 for ; Sat, 04 Jan 2014 07:27:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=4GdG1kK6edqSYFiFIGhv79OMlWiJjnFT3f5WAWCrvUk=; b=At9dIPCth8S31BXOXHK9/96RnuzdCabHGkJq4xj4o6J0VJPzP9lpTFoJJyfpb8UWj2 Wl0bHi4jL3TJtlfndEWdVRIcm2UviXwSfZTAmyZjzU8U8KerBSAdLpyCYF9oatpL5tYs 6TqleAPJGtfV3OHCHjugPG4qszRRh8n0ain7E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=4GdG1kK6edqSYFiFIGhv79OMlWiJjnFT3f5WAWCrvUk=; b=ItR3CgBnFkMPlGdnkKsFYDTcZ0v4oSwEYW9mYGmLPOIVQFNU0EkMr6HAvblFHnJqdH +2N/tRzFXJ+xGtxmvarTFz0020D9WEmK1iyU3byCuJqeq99ymG4u83FNcHowhc367eYi /YUR5A/PEyr0uZecIrqHaPeEVB+jhru8K2ggC73ja1N0kycCU864GQWYPDvUdoCvM0Vp fWmOAHpQUNFPrIq3ZY1AAZrPV3mSVJlVGHlyHqEnQHPwS6GjSd2t9q1pcZbVGIVD2TOb 4QVqCx0TyqZrXSrHUXHHdnHGYxhwTSdi4x85qOSYWnYPufnBzueOjGHZbqMGhY8aXXDm z8RQ== X-Gm-Message-State: ALoCoQkJCsa87be1Wra2RRZuJ4ouNdrUWWbRywuuvA19cBCoQOJXv+lErYU9RlMbgbhAyn+0Zqak X-Received: by 10.224.39.18 with SMTP id d18mr93844525qae.97.1388849279429; Sat, 04 Jan 2014 07:27:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.82.166 with HTTP; Sat, 4 Jan 2014 07:27:39 -0800 (PST) In-Reply-To: References: From: Lahiru Sandaruwan Date: Sat, 4 Jan 2014 20:57:39 +0530 Message-ID: Subject: Re: [Autoscaler] HealthEventMessageDelegator doesn't follow the correct message processor pattern To: "dev@stratos.incubator.apache.org" Content-Type: multipart/alternative; boundary=001a1134a274f28aa104ef26abfc X-Virus-Checked: Checked by ClamAV on apache.org --001a1134a274f28aa104ef26abfc Content-Type: text/plain; charset=ISO-8859-1 Final bit of the fix is added with commit 253bbb08a9fab307570a2832cc965757384e0422. Now all the message receivers in Autoscaler follow chain of responsibility pattern. Also I have added all the required bits in messaging components such that if any other party wants Health stat messages. Example message that would required from CEP side would be, {"org.apache.stratos.messaging.event.health.stat.MemberAverageLoadAverageEvent":{"message":{"memberId":"member_id","value":3.3}}}} Manula will do necessary changes in CEP side to send events this way. On Fri, Dec 20, 2013 at 2:02 PM, Lahiru Sandaruwan wrote: > I'm working on adding message events and processors in messaging component > for health stat events. > > Thanks. > > > On Fri, Dec 6, 2013 at 11:35 AM, Lahiru Sandaruwan wrote: > >> I'm starting with Scale up/ down algorithms etc. So i'll look into this >> as well.. >> >> Thanks. >> >> >> On Fri, Dec 6, 2013 at 11:32 AM, Nirmal Fernando wrote: >> >>> All, >>> >>> Just noticed that $subject. Idea of introducing message processor chain >>> [1] is to avoid if-else statements and follow a proper OOP design pattern. >>> >>> Can anyone volunteer to fix this bit of code? >>> >>> [1] dev@ thread: Topology Event Message Processors follow 'chain of >>> responsibility' design pattern >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> Nirmal Fernando. >>> PPMC Member & Committer of Apache Stratos, >>> Senior Software Engineer, WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> >> >> -- >> -- >> Lahiru Sandaruwan >> Software Engineer, >> Platform Technologies, >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> email: lahirus@wso2.com cell: (+94) 773 325 954 >> blog: http://lahiruwrites.blogspot.com/ >> twitter: http://twitter.com/lahirus >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > > > -- > -- > Lahiru Sandaruwan > Software Engineer, > Platform Technologies, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > email: lahirus@wso2.com cell: (+94) 773 325 954 > blog: http://lahiruwrites.blogspot.com/ > twitter: http://twitter.com/lahirus > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 > > -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahirus@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 --001a1134a274f28aa104ef26abfc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Final bit of the fix is added with commit=A0253bbb08a9fab3= 07570a2832cc965757384e0422.

Now all the message receiver= s in Autoscaler follow chain of responsibility pattern. Also I have added a= ll the required bits in messaging components such that if any other party w= ants Health stat messages.

Example message that would required from CEP side would= be,

{"org.apache.stratos.messaging.event.hea= lth.stat.MemberAverageLoadAverageEvent":{"message":{"me= mberId":"member_id","value":3.3}}}}

Manula will do necessary changes in CEP side to s= end events this way.


On Fri, Dec 20, 2013 at 2:02 PM, Lahiru Sandaruwan <lahi= rus@wso2.com> wrote:
I'm working on adding m= essage events and processors in messaging component for health stat events.=

Thanks.
<= div class=3D"gmail_extra">

On Fri, Dec 6,= 2013 at 11:35 AM, Lahiru Sandaruwan <lahirus@wso2.com> wrote= :
I'm starting with Scale= up/ down algorithms etc. So i'll look into this as well..

Thanks.


On Fri, Dec 6, 2013 at 11:32 AM, Nirmal Fernando <nirmal070125@gmail.com> wrote:
All,
Just noticed that $subject. Idea of introducing message= processor chain [1] is to avoid if-else statements and follow a proper OOP= design pattern.

Can anyone volunteer to fix this bit of code?

[1] dev@ thread: Topology Event Mes= sage Processors follow 'chain of respo= nsibility' design pattern

--
Best Regards,
Nirmal

Nirmal Fernando.=
PPMC Member & Committer of Apache Stratos,
Senior Software Engin= eer, WSO2 Inc.




<= font color=3D"#888888">--



--
--
Lahiru Sandaruwan
Softw= are Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahirus@wso2.com cell: (+94) 773 325 95= 4
blog: http:= //lahiruwrites.blogspot.com/
twitter: http://tw= itter.com/lahirus
linked-in: http://lk.linkedin.com/pub/l= ahiru-sandaruwan/16/153/146




--
=
--
Lahiru Sandaru= wan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahirus@wso2.com cell: (+94) 773 325 954
blog: <= a href=3D"http://lahiruwrites.blogspot.com/" target=3D"_blank">http://lahir= uwrites.blogspot.com/
twitter: http://tw= itter.com/lahirus
linked-in: http://lk.linkedin.com/pub/l= ahiru-sandaruwan/16/153/146

--001a1134a274f28aa104ef26abfc--