On Mon, Jun 16, 2014 at 9:28 AM, Lahiru Sandaruwan <[email protected]> wrote:
> +1 for a lightweight agent. > > AFAIR blocker for #2 was reading message headers. We might need to address > that as first step for #2. > > Sometimes back I had worked with some message broker clients which use AMQP. As you mentioned blocker was sending and reading message headers. Will work on it to find a proper solution Thanks. > > > On Mon, Jun 16, 2014 at 9:17 AM, Dinesh Bandara <[email protected]> wrote: > >> Hi Devs, >> >> We have discussed about the importance of a light weight cartridge agent >> in several mail threads since existing agent had been written in Java and >> running a Java runtime inside a cartridge instance is a performance >> overhead as well as a costly operation. Here I would like to initiate that >> (writing a Python based cartridge agent) with the requirements which mainly >> required for it. >> >> First of all we have to implement Python clients for the communication >> mechanisms used in agent. Cartridge agent mainly use two communicate >> mechanisms, >> >> 1. Communicate with Complex Event Processor using thrift >> 2. Communicate with Message Broker using AMQP >> >> To full fill the requirement #1, we have to write a python thrift client >> and I'm currently working on it. >> >> Highly appreciate your thoughts on this. >> >> Thanks, >> -- >> *Dinesh Bandara* >> Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> > > > -- > -- > Lahiru Sandaruwan > Committer and PMC member, Apache Stratos, > Senior Software Engineer, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > email: [email protected] 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 > > -- *Dinesh Bandara* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware
