the state pattern

The state pattern becomes useful if your object needs to react differently to different states. Let us assume you are writing an SMTP Proxy. SMTP works in sequences (connection establishment, ehlo/helo, mail, rcpt, data(, …), quit). Each sequence can have different error/success codes which are not available in another. For example you would only return 220 on connection establishment, not 250. And you would return 221 on quit, not 250. So if you are writing a server which works like this, you will most likely use an if then else or switch. The state-pattern would be another method to solve this. However, a more simple example which shows the pros and cons of the state pattern is an activity-based-sleep.
Continue Reading

Manually written forms and the request token

See, that’s for example something I do dislike at Contao. The documentation for developers sucks. Even simple things like adding the request-token to your self-written forms is not documented or I am absolutely blind. I also have the feeling that they (people who wrote the documentation) assume that a developer will read Contao’s source code if he/she has any questions. That’s like assuming a cleaning-lady checks the mechanics of a vacuum cleaner to see how it works. Anyway:

Continue Reading