Entries Tagged ‘Object-oriented development’

Securing Web Services

Last week I wrote my first web service (yay!). I am not going to write about that, as process of creating web services is nicely described at IBM developerworks. But, back to my service. The service is used to do some work that only my consumer application should be able to do. However, due to […]

Design patterns – Part 3: Singleton pattern

The simplest way to describe singleton class is to look at the definition: The Singleton Pattern ensures a class has only one instance, and provides a point of access to it. So why would you need that? Well, there are many objects you only need one of in your application (e.g. Logging, text trimming, for […]

Design patterns – Part 2: Decorator pattern

For those, skilled in Java development, Decorator patterns are nothing new, as they are quite common in Java, i.e. FileInputStream with it’s decorator BufferedInputStream class. The definition says: The Decorator Pattern attaches additional responsibilities to an object dynamically. More theoretical background can be found on Wikipedia.

Design patterns – Part 1: Strategy pattern

One of the simplest and most commonly used patterns is definitely strategy pattern. We cannot pass a boring definition, so here you go: The Strategy Pattern defines a family of algorithms, encapsulates each one, and makes them interchangeable. Strategy algorithm vary independently from clients that use it. You will find out that all strategy pattern […]

Design patterns and LotusScript

Design patterns are here to ease work to us developers. They present already made solutions to known problems. I will not go into philosophical debate about why they are practically not used in LotusScript. Instead, in future articles, I will try to present basic design patterns translated to LotusScript. For those that are already interested […]