[Dev] [MB] Adding the capability to enable/disable message status

[Pamod Sylvester]

Hi All,

Currently in OnflightMessageTracker we have a list of message statuses
maintained under MsgData. Based on the current observation, these statuses
are being only used to dump it to a file, mainly for debugging purposes.
The method gets invoked each time a message is delivered to
subscriber/subscribers and the addition of the status should be a
synchronous call.

Would it be safe to move this into the configuration, giving the option to
the users to enable it ?

Thanks,
Pamod

-- 
*Pamod Sylvester *

*WSO2 Inc.; http://wso2.com *
cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Adding the capability to enable/disable message status

[Ramith Jayasinghe]

In my opinion we need to check if we really need keep the history in
on-flight-message tracker.
If we can wire up the enums (at compile time) to model the state
transitions then we don't need to use this ( - just like we did for
SlotState)
thoughts?

On Thu, May 28, 2015 at 4:09 PM, Pamod Sylvester  wrote:

> Hi All,
>
> Currently in OnflightMessageTracker we have a list of message statuses
> maintained under MsgData. Based on the current observation, these statuses
> are being only used to dump it to a file, mainly for debugging purposes.
> The method gets invoked each time a message is delivered to
> subscriber/subscribers and the addition of the status should be a
> synchronous call.
>
> Would it be safe to move this into the configuration, giving the option to
> the users to enable it ?
>
> Thanks,
> Pamod
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com *
> cell: +94 77 7779495
>



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev