Damn! Pull messaging doesn't work in STOMP:
https://groups.google.com/forum/?fromgroups=#!searchin/stomp-spec/pull$20message/stomp-spec/-mVMJEOuay4/tUUW6wjzn0sJ

Back to JMS:(

On Sat, Jan 12, 2013 at 11:13 AM, Mridul Jain <[email protected]> wrote:

> I have to replace some existing messaging system with Kafka and the
> applications running on top are/would be either JMS or STOMP compliant in
> different languages. I am looking for simple capabilities with Kafka
> high-level client apis give and not anything fancy/transactional like
> ActiveMQ as our main requirement is scale and performance.
> I have to start working on the exact list of features though...just have a
> high-level requirement right now and evaluating options. I do use Kafka for
> my platform with storm and high level client apis; but other apps which
> want to get onto this for subscription, use ActiveMQ via JMS apis today or
> might be even STOMP compliant.
>
> Thanks
>
>
> On Sat, Jan 12, 2013 at 10:55 AM, Jun Rao <[email protected]> wrote:
>
>> Right now, there is no such plan. What features are you looking for by
>> using STOMP?
>>
>> Thanks,
>>
>> Jun
>>
>> On Fri, Jan 11, 2013 at 9:15 PM, Mridul Jain <[email protected]>
>> wrote:
>>
>> > Is there any plan or interest in the following...if yes, I might solicit
>> > some review as I have a need for STOMP binding and might have to
>> develop it
>> > anyway.
>> >
>> > Thanks
>> > Mridul
>> >
>> > On Sat, Jan 12, 2013 at 10:38 AM, Jun Rao <[email protected]> wrote:
>> >
>> > > Kafka currently doesn't support those.
>> > >
>> > > Thanks,
>> > >
>> > > Jun
>> > >
>> > > On Fri, Jan 11, 2013 at 8:37 PM, Mridul Jain <[email protected]>
>> > > wrote:
>> > >
>> > > > hi,
>> > > > Is there a STOMP/JMS binding for Kafka? I was following the thread
>> > below:
>> > > >
>> > > >
>> > >
>> >
>> http://mail-archives.apache.org/mod_mbox/incubator-kafka-dev/201109.mbox/%3ccahpe1evmz5ghbsmgbqyrj+q3s17te_yfjuckv+e8jshykp+...@mail.gmail.com%3E
>> > > >
>> > > > But it is inconclusive.
>> > > >
>> > > > - Mridul
>> > > >
>> > >
>> >
>>
>
>

Reply via email to