Hello Steven, Thanks for your suggestions, I have certainly seen other stack/presentation where people do forward their messages to their own receiver which forwards the message to kafka -- basically they write their own producer(s).
The question I haven't been able to answer for myself- why -- doesn't this introduce another set of thing that can fail, and needs to be may be managed by zookeeper in case it goes down etc? Because in the end all this app-server is doing is taking messages from remote clients and forwarding it Kafka -- hence the doubt in my mind of value of introducing something else in the middle. In spite of this doubt got any suggestions for app-server that can send received messages to kafka? Regards, -Subodh On Wed, Jul 16, 2014 at 6:32 PM, Steve Robenalt <sroben...@highwire.org> wrote: > Hi Subodh, > > I would think you'd be better off having an app server of some kind as an > intermediary that accepts messages from your android app and posts them to > Kafka for you, rather than having your app be a Kafka Producer on its own. > > Steve > > > On Wed, Jul 16, 2014 at 1:22 PM, Subodh Nijsure < > subodh.nijs...@sigsensetech.com> wrote: > > > Hello, > > > > I am trying to make my Android application to be the producer of messages > > that get sent to Kafka server. > > > > I am trying to compile my android code using following libraries - > > kafka_2.9.2-0.8.1.1.jar, scala-library-2.9.2.jar > > > > However I am running into issue where it produces too many methods. > > > > So the question: > > > > Has anyone been successful in sending messages form Android application > to > > server. If I want to trim the libraries should I be just compiling source > > myself or is there and/or any other alternative I should look at to get > my > > android app to send message to Kafka server. > > > > -Subodh > > >
