Using ETags

With an Etag (or Entity Tag) it is possible to check with the server if a resource has changed the last time it is received. The server sends an Etag in the headers of the request when a resource is received. A md5 sum of the content is a good candidate for a Etag because it changes when the content changes. It could be useful when the resource is not static but it will not change very often. The controller in a web application can perform the ETag comparison and decide when to send a the resource or a not modified. Continue reading Using ETags

The problem with dynamic languages and large projects

Abstract: In large projects it is important to find unused and old code and remove those pieces of code. With dynamic languages this is virtually impossible. It is important to clean and refactor unused parts of a system because this can become a security risk. Also a lot of “noise” is added to the system that makes it more difficult to understand the system.

While working on a large project I have the need to find pieces of code that are no longer in use. With a dynamic language and specific PHP this is virtually impossible and below I will give an explanation why that is. Continue reading The problem with dynamic languages and large projects