+1


Touched, not typed. Erroneous words are a feature, not a typo.
On Nov 17, 2014 10:51 AM, "Lahiru Sandaruwan" <[email protected]> wrote:

> +1
>
> On Mon, Nov 17, 2014 at 10:41 AM, Vishanth Balasubramaniam <
> [email protected]> wrote:
>
>> +1
>>
>> On Mon, Nov 17, 2014 at 10:01 AM, Lakmal Warusawithana <[email protected]>
>> wrote:
>>
>>> +1
>>>
>>> On Mon, Nov 17, 2014 at 7:53 AM, Chamila De Alwis <[email protected]>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Shall we have $subject? I'm looking at 2.30pm - 3.30pm on Wednesday
>>>> 19th November 2014. Is this a feasible time frame?
>>>>
>>>> I intend to cover the initial design of the Python agent, specifics
>>>> related to the Python agent, and what is different from the Java agent.
>>>> Although the functionality is the same, there are differences between the
>>>> Python agent and the Java agent, especially with regard to the
>>>> implementation, code structure, and how it communicates with Stratos.
>>>>
>>>> Since there is development still being going on with the Python agent,
>>>> I intend to extend this to another hangout where a deep look at the code on
>>>> functionality like artifact management and health stat publishing.
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Vice President, Apache Stratos
>>> Director - Cloud Architecture; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>
>>
>> --
>> *Vishanth Balasubramaniam*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94771737718*
>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: [email protected] blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>

Reply via email to