On Wednesday 18 February 2004 19:39, Leo Simons wrote:
Thanks for the long RT on what constitutes a Request/Response architecture,
hehehe. Well the point is looking at request/response from the IoC view of the world, innit?
but IMHV, isn't this just an generalization (i.e. using something else than the heap and stack, as transport) of normal call/returns of most programming languages?
it's all turing-equivalent :D
what's important is the way we think about these things. When I look at most implementations in this field, I often think "well, that's just all the same". But that doesn't really help us get anywhere ;)
When I think of "Event-Driven" programming patterns, it boils down to exactly what you have described in your essay about why Loggers are no good (I loved that one, and a real eye-opener of something one have taken for granted!).
that was Leo Sutic's essay :D
And I think Alex has noticed that, and seen that the next level is the 'router'/'hub', gives even more decoupling benefits.
yep. And the next point is decoupling 90% of the code from being aware of the router ;)
Join my Advanced Course ;o)
I study physics dude. With software I'm only interested in long-winded and preferably unfounded discussion and thought exchange that have no basis in knowledge. I thought you had that figured out by now ;)
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://articles.leosimons.com/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
