[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    Re: [jdev] parsing xml (xmpp) with ruby
From:       Jonathan Dickinson <jonathan.dickinson () k2 ! com>
Date:       2008-10-03 12:29:16
Message-ID: A790BE8D83ECC3469047C2E344EABE61D20B755310 () zamail01 ! k2workflow ! com
[Download RAW message or body]

> -----Original Message-----
> From: jdev-bounces@jabber.org [mailto:jdev-bounces@jabber.org] On
> Behalf Of Remko Tronçon
> Sent: Friday, October 03, 2008 2:24 PM
> To: Jabber/XMPP software development list
> Subject: Re: [jdev] parsing xml (xmpp) with ruby
> 
> ... Only resort to
> threads when you *really* have a problem that can only be solved with
> adding threads.

Amen.

> Otherwise, stay away from it if you want to maintain
> your sanity.

Amen, again.

> I doubt that the poster's software project is already in
> that stage where he needs threads to solve his problems.

I beg to differ. It's a daemon, it will be a nightmare to refactor into threads if he \
takes it any further. It is a choice he has to make, but it won't scale horizontally \
unless more machines/process instances are added.

> 
> cheers,
> Remko
> _______________________________________________
> JDev mailing list
> FAQ: http://www.jabber.org/discussion-lists/jdev-faq
> Forum: http://www.jabberforum.org/forumdisplay.php?f 
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe@jabber.org
> _______________________________________________
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f 
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe@jabber.org
_______________________________________________


[prev in list] [next in list] [prev in thread] [next in thread]