Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Re: Component-based architecture in Perl

by crenz (Priest)
on Jul 05, 2005 at 20:02 UTC ( #472585=note: print w/replies, xml ) Need Help??


in reply to Component-based architecture in Perl

I'm not quite sure how useful the component approach is, but that might be because I might not have fully understood it. If you have classes that all behave the same, aren't they subclasses of a common parent? And in that case, I can treat them all the same (where they share the same interface of the parent). So why is there a need to handle this case specially?

  • Comment on Re: Component-based architecture in Perl

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://472585]
help
Chatterbox?
[Corion]: thezip: Yeah - we have "CAP", but that means "Change Ablauf Plan" (Change Sequence Plan). Likely there is a true ITIL name for this too.
[Corion]: While I'm not really a fan of ITIL, it certainly is better than nothing and it at least provides a common vocabulary, so if you have ITIL somewhere at your disposal, it might be worth a look
[Corion]: Hmm - that should be somewhere in the "Release Deployment Plan", but I don't find a good English link (nor a good German one ;) )

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (10)
As of 2017-02-23 17:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Before electricity was invented, what was the Electric Eel called?






    Results (350 votes). Check out past polls.