Is there a new snapshot out with this change?
--jason
On Feb 25, 2007, at 12:42 AM, Hiram Chirino wrote:
Well,
I've moved the existing broker time stamp logic to a
TimeStampingBrokerPlugin. Anyone who depended on ActiveMQ 4.1.0's
broker time stamping behavior will now have to enable the
"timeStampingBrokerPlugin" in their broker configuration in subsequent
releases.
On 2/25/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Why not optional with a different property, so that the spec behavior
is always consistent, but users can still get the custom data they
need if the broker has some flag flipped on?
This sounds like a cleaner approach, but since the behavior is
different would need to be implemented a different plugin, or an
option enabled on the TimeStampingBrokerPlugin.
--jason
On Feb 24, 2007, at 11:54 PM, Rob Davies wrote:
> It was requested by a some users - they wanted to compare messages
> from different producers on different machines by time sent - and
> as the clients clocks aren't in sync, they really needed the
> timestamp set on the broker. I guess the best thing to do would to
> make it optional, off by default
>
> cheers,
>
> Rob
>
> On 25 Feb 2007, at 07:43, Hiram Chirino wrote:
>
>> Rob, do you remember why added the following feature?
>> http://svn.apache.org/viewvc?view=rev&revision=376260
>>
>> Setting the time on a message can break JMS spec compliance,
plus it
>> forces us to have the overhead of getting the system time on every
>> message sent. I was hoping we could roll this one back.
>>
>> --
>> Regards,
>> Hiram
>>
>> Blog: http://hiramchirino.com
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
