I was proposing to set a default per queue, but allowing a fine controlled
per-message override.
Chris
-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com]
Gesendet: Sonntag, 26. Juli 2015 17:32
An: dev@flex.apache.org
Betreff: Re: Changes to BlazeDS addressing memory
This is totally outside my area of expertise but just so I’m clear, are
you proposing weak references or hard references on a per-message basis,
or that the queue uses weak or strong for all of its messages?
If the former, that makes sense to me. If the latter, I would be
concerned that it would
Hi,
I am currently digging into some of the problems reported to BlazeDSs memory
consumption. While there seems to be a real problem in the cleanup of clients,
there is one other problem that could eventually help systems with a high
throughput of messages.
Usually messages for a client are
