On Thu, Oct 22, 2009 at 10:20 AM, Samisa Abeysinghe <[email protected]> wrote:

>
>
> On Thu, Oct 22, 2009 at 9:39 AM, Hiranya Jayathilaka <[email protected]>wrote:
>
>>
>>
>> On Thu, Oct 22, 2009 at 8:17 AM, Ruwan Linton <[email protected]> wrote:
>>
>>> Samisa Abeysinghe wrote:
>>> > When the mediation stat component collect data, it clears the lists
>>> > using Synapse API.
>>> >
>>> > When the BAM publisher module collect the data, if it does not clear
>>> > the data, then it happens to recount some of the records that is
>>> > already counted. So I also have to clear the lists. Which means, if
>>> > BAM publisher is present, the mediation stat module would not function
>>> > as expected.
>>> Didn't we already discussed this :-) and Hiranya is working on a
>>> solution.
>>>
>>
>> Well the problem here is that BAM components are pulling data directly
>> from Synapse using a handler. They are not using the mediation-statistics
>> admin services. So I think even if we make the proposed changes to the
>> mediation-statistics component, BAM stuff won't benefit  from those
>> improvements.
>>
>
> In the eventing model, it does not make sense to pull data from a store. It
> has to be real time. This is why the BAM puller is pulling data from Synapse
> layer and not the mediation stat admin. So it is not a problem in design in
> terms of eventing.
>
> May be the stat module could use the same eventing model. So that, it can
> either fire the event, store it as desired or both. However, also note that,
> we also discussed about getting rid of storing stats into the registry in
> ESB, in another discussion.
>

+1. This is what I meant by  'proposed changes' in my previous mail.

Thanks,
Hiranya


>
> Samisa...
>
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>> Thanks,
>>> Ruwan
>>> >
>>> > Samisa...
>>> >
>>> > --
>>> > Samisa Abeysinghe
>>> > Director, Engineering - WSO2 Inc.
>>> >
>>> > http://www.wso2.com/ - "The Open Source SOA Company"
>>> >
>>> ------------------------------------------------------------------------
>>> >
>>> > _______________________________________________
>>> > Carbon-dev mailing list
>>> > [email protected]
>>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >
>>>
>>>
>>> --
>>> Ruwan Linton
>>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>>> WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org
>>> email: [email protected]; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>>
>>>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: [email protected];  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: [email protected];  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to