|
|
| Author |
Message |
< RabbitMQ mailing list ~ Daemonizing connection threads (was .Net client foreground |
| Guest |
 Posted: Thu Jan 07, 2010 1:56 pm |
 |
|
|
Guest
|
On Thu, Jan 07, 2010 at 01:28:03PM +0000, Tony Garnock-Jones wrote:
> > The alternative is that you
> > sometimes see messages disappear without trace which is far worse, and
> > much harder to debug.
>
> Well that's true. Perhaps the non-auto-buffer-flushing behaviour around
> sockets is simply (yet another instance of) premature optimisation from
> the Java library designers?
Well, the recent ext3/4 "ZOMG closing a file doesn't sync its
content!!!eleven!!" revelations demonstrate that people will rely on
observed behaviour even if it's not guaranteed. For this reason alone, I
think that forcing people to close the connection is "the right thing"
on the grounds that the non-deterministic "you may lose messages, or you
may not" alternative leads to the ext3 situation. If things then changed
in the client to make it much more likely to lose messages in this
situation (now ext4) then people will complain. Far safer to ask users
to tidy up correctly in the first place. Yes, it may be un-Java-like,
but then again so is much good programming practice. 
/me throws fuel on fire and runs...
Matthew
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
