If like you said, --totally tightly coupled solution is overkill.--
,than I can agree with you :P
But alright, to plug in on this matter. As I found out it's not hard to
lose the tight coupling.
The hard part is to find a system that works fast and intuitive for you.
Once you found or
Tight coupling is not as bad as people make it out to be.
Yes it is.
Jason Merrill
Bank of America Global Learning
Learning Performance Soluions
Join the Bank of America Flash Platform Community and visit our
Instructional Technology Design Blog
(note: these are for Bank of America
Merrill, Jason wrote:
Tight coupling is not as bad as people make it out to be.
Yes it is.
No, it is not. Btw, thanks for your very stimulating response. Meh, I
get to argue for my point first then.
Tight coupling can be an issue, if the coupled components shouldn't be
coupled. It is not
On Tue, Nov 17, 2009 at 8:06 PM, Henrik Andersson he...@henke37.cjb.net wrote:
Tight coupling can be an issue, if the coupled components shouldn't be
coupled. It is not an issue at all if they more or less couldn't work
without something doing the job of the other and few if any replacement
Ian Thomas wrote:
In which case they're actually one component, conceptually - if the
dependencies are really that inextricable. :o)
Two sub modules in a webbrowser is a http client and an image parser.
Yet, they need to cooperate for images to download while being displayed.
When do you
*blink*
But those two components should not be tightly coupled.
Bad example, I think.
The HTTP client doesn't depend on the image parser; it's used to
provide HTTP services to a number of different components of a
browser. You could use the HTTP client code in complete isolation from
knowing
Alright, since I asked the question, I'm piping in. I just finished a project
that became immensely complicated precisely because I eventually had everything
tightly coupled. Had I used custom events and done some other things from the
get go, I'm nearly certain it would have been easier to
Ian Thomas wrote:
stuff
My point is that things that can seem unrelated can have a direct
relationship anyway. The image parser can run alone, yes. But it needs
to cooperate with the http client module if you want to show the image
while it is still loading. That was my point of the
Sorry, we're way off topic here. :-D I'll shut up.
Ian
On Tue, Nov 17, 2009 at 9:05 PM, Mendelsohn, Michael
michael.mendels...@fmglobal.com wrote:
Alright, since I asked the question, I'm piping in. I just finished a
project that became immensely complicated precisely because I eventually
I completely agree with this as I've been in exactly the same
situation with a largish scale project. The sort of projects I tend to
do are small scale games for which the totally tightly coupled
solution is overkill. However, I've eaten my words on that point as
well...
On 17 Nov
10 matches
Mail list logo
