Forum Post: AW: AW: Static Class Code Libraries (or Smarter Ways to Manage Business Logic)

[Mike Fechner]

I still believe we need to learn more from the OP about what he intended in those statics. What runtime considerations are you talking about ABL vs. Java that are relevant for static classes in particular? The ABL is slower in loading classes compared to Java and .NET. That’s a fact and that leads to a more important role of temp-tables and ProDatasets in modern architectures. But especially with static classes, the overhead in instantiation is pretty much ignorable. We use a hand full of utility classes that are static. We consider them extensions of the language. And I don’t have problems with that. All framework and business logic classes are non static. That’s a different domain and can IMHO be implemented differently. Von: Tim Kuehn [mailto:bounce-timk519@community.progress.com] Gesendet: Dienstag, 14. Oktober 2014 12:10 An: TU.OE.General@community.progress.com Betreff: Re: [Technical Users - OE General] AW: Static Class Code Libraries (or Smarter Ways to Manage Business Logic) Re: AW: Static Class Code Libraries (or Smarter Ways to Manage Business Logic) Reply by Tim Kuehn On Tue, Oct 14, 2014 at 3:02 AM, Mike Fechner wrote: I didn’t expect you not to disagree with me. Beg my pardon, when I get the feeling that the OP has OO experience, I tend not to put his question down like a stupid boys question like some others tend to do in forums. The OP may have OO experience, however there are run-time considerations when doing ABL code which are different from Java run-time considerations. For instance, upgrading an appserver-based application, where the "scope of the session" is the agent's lifetime, not a single user's session. Using statics in that scenario has caused lots of problems when it's time to replace static-based or dependent code with something else, particularly if TT changes are involved. -- Tim Kuehn: Senior Consultant - TDK Consulting Services Ontario PUG President PUG Challenge Americas Executive, Program Committee Chair Skype: timothy.kuehn Ph: 519-576-8100 Cell: 519-781-0081 Stop receiving emails on this subject. Flag this post as spam/abuse.

Continue reading...