Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [messaging-dev] Browsing / Streaming...

The current constraints of Browsing are : you consume every single message on the destination, without actually consuming them...

While a Consumer will be polling messages.. so if two consumers are connected.. one will receive half.. and the other consumer the other half.



At this point it seems to a good idea to have these two concepts differentiated... Queuing and Streaming..  


Browsing from the current JMS implementation would be replaced by the idea of Streaming.


Browsing is using a Java Iterator... the Streaming could also be using that moving forward.



As for MDBs.. that's probably an orthogonal design to this. (something similar to MessageListeners.. but that's a separate discussion).

On Thu, Mar 13, 2025 at 11:09 AM Reza Rahman via messaging-dev <messaging-dev@xxxxxxxxxxx> wrote:
I would first need to understand more about the use case to be honest.

Is this the same as the existing browsing use case or is it actually consuming messages off a queue? If the latter, this would be an imperative alternative to MDB style declarative message consumption?


From: messaging-dev <messaging-dev-bounces@xxxxxxxxxxx> on behalf of Clebert Suconic via messaging-dev <messaging-dev@xxxxxxxxxxx>
Sent: Thursday, March 13, 2025 11:00 AM
To: Matt Pavlovich <mattrpav@xxxxxxxxx>
Cc: Clebert Suconic <csuconic@xxxxxxxxxx>; EE4J Messaging project developer discussions <messaging-dev@xxxxxxxxxxx>
Subject: Re: [messaging-dev] Browsing / Streaming...
 
well.. you have things on a certain context... 

you could maybe even reuse some of the Java Streams API, expand perhaps?

On Thu, Mar 13, 2025 at 10:43 AM Matt Pavlovich <mattrpav@xxxxxxxxx> wrote:
Naming is hard! The first thing that jumped out at me is that ’streaming’ is confused with the Java ’streams’ language feature. I lean towards ‘Event’ since it is shorter (and not as over loaded).

Matt Pavlovich

> On Mar 12, 2025, at 2:40 PM, Clebert Suconic via messaging-dev <messaging-dev@xxxxxxxxxxx> wrote:
>
> I'm planning to spend some time next week writing some ideas...
>
>
> But before I spend time on it.. I wanted to ask something...
>
>
> There's the concept of a Browser in the current JMS API. What if we called it Streaming?
>
> You would have a differentiation between Queueing semantics (single destination polling messages between multiple endpoints) and Streaming semantics where all the messages from the destinations are received.
>
> It's the same concept in the end.. but maybe Streaming would be a better name for a newer API.
>
>
>
> _______________________________________________
> messaging-dev mailing list
> messaging-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://accounts.eclipse.org

_______________________________________________
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

Back to the top