On Tue, 2007-12-18 at 19:31 -0500, marius schebella wrote:
I think connections are slightly faster, but that is negligible. the more important aspect is programming style/readability/layout/program flow, and in this respect connections are definitely preferable. with send/receive you end up with spaghetti code. Maybe when working with a lot of abstractions, it makes sense to use send/receive, just because drawing too many connections is a pain. but most of the time connections make your life easier. marius.
maybe when working with a lot of abstractions, it makes sense to use methods, that are all sent to the same inlet and inside the abstraction [route]d apart again. it makes it also easier to debug, because you need to create only one connection to one [print] in order to see, which message is sent in what orde to the abstraction.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de