Yesterday I attended the 3rd European Workshop on Aspects in Software at the University of Twente in Enschede, The Netherlands where I presented a paper titled GAP: Generic Aspects for PHP that is co-authored by Günter Kniesel and myself.

The workshop was organized as a Writer's Workshop. This means that every attendee is required to read your paper beforehand so that they can discuss it properly after you gave a short presentation. I enjoyed this format and am thankfull for the usefull feedback I got from my peers.

Since I work at eZ systems AS on my Diploma Thesis for the University of Bonn, this paper can be seen as a cooperation of eZ systems AS and the University of Bonn.

Yesterday I attended the 3rd European Workshop on Aspects in Software at the University of Twente in Enschede, The Netherlands where I presented a paper titled GAP: Generic Aspects for PHP that is co-authored by Günter Kniesel and myself.

The workshop was organized as a Writer's Workshop. This means that every attendee is required to read your paper beforehand so that they can discuss it properly after you gave a short presentation. I enjoyed this format and am thankfull for the usefull feedback I got from my peers.

Since I work at eZ systems AS on my Diploma Thesis for the University of Bonn, this paper can be seen as a cooperation of eZ systems AS and the University of Bonn.

Yesterday I attended the 3rd European Workshop on Aspects in Software at the University of Twente in Enschede, The Netherlands where I presented a paper titled GAP: Generic Aspects for PHP that is co-authored by Günter Kniesel and myself.

The workshop was organized as a Writer's Workshop. This means that every attendee is required to read your paper beforehand so that they can discuss it properly after you gave a short presentation. I enjoyed this format and am thankfull for the usefull feedback I got from my peers.

Since I work at eZ systems AS on my Diploma Thesis for the University of Bonn, this paper can be seen as a cooperation of eZ systems AS and the University of Bonn.

The International PHP Magazine has posted the results of the question asked in their latest poll - "What is the Top Criterion for Scaling PHP?"

Of the six options they provided:

• Object code caching
• Template systems
• Distributed object-caching systems
• PHP variables that can be set
• Output Compression
• Other things that may help

one stood out as a clear winner - "Object code caching". Bringing up second place was "Distributed object-caching systems" and the other options coming in pretty close behind.

Be sure to cast your vote for their latest poll question - "Which is the Most Common Database Problem?"

The biggest news from eZ this week is the release of eZ components version 1.1.1. We also have news about the CLA (Contributor Licensing Agreement), the weekly forum watch and an update on the current bug status.

Nefarious Designs continues their object-oriented PHP series with part four posted today, a look at some of the new features that PHP5 brings to the table.

After a welcome break, over the late summer public holiday here in England, here's the final part in my object-oriented PHP series. Sorry about the rather extended pause since "Part 3: Taking Relationships Further".

Having already looked at definition, relationships and taking those relationships further, I'm going to look at how PHP5's new Object Model introduces more advanced functionality.

In this latest part they look at clas constants, abstract classes, object interfaces, and magic methods (including overloading).

Continuing on in their latest series (begun with this part), DevShed has posted part two of their look at working with files in PHP - "Uploading Files and Navigating Directories in PHP".

They jump right in, giving you the needed settings for your php.ini file to get the examples to work (mainly for the file uploads). They explain what a file upload form looks like and what some of the potential error codes could be.

The code comes next, showing a simple file upload form taking in the file, moving it off to another directory, and if there are errors, displaying them. The next obvious step up from a single file upload is the multiple file upload, and they show how to use PHP's form handling of arrays to accomplish this.

Finally, they include a simple little script to read the directory the files are in and display the information about them (like size file, name, and modified date).

Ilan Rabinovitch let me know that the SCALE team is getting started on version 5x of the SoCal Linux Expo. In past years, SCALE has been a great community event - the ratio of promoters to real Linux enthusiasts is low and the attendees are friendly. Also, like most other Linux conferences, attendees have a strong [...]

Ever wondered just how many PHP frameworks there are out there? Well, this mapping of them gives you a good idea. ColdScripts.com has created a single page, digg-ish voting system for lots of the PHP frameworks out there, letting users pick their favorites.

The brighter/clearer the framework's information, the higher it's ranking. To cast a vote, just click on the "+" (plus) in the box for your choice, or the "-" (minus) to detract from the score.

So far, it looks like CakePHP and Symfony are tied in the lead with Code Igniter and eZ Components following close behind. Be sure to head over and vote for your favorite framework today!

En publiant mon précédent billet L'électronique et l'environnement , je me suis rendu compte que la liste des deniers billets sur la page d'accueil de ce site n'était pas mise à jour. Ce petit problème vient en fait du cache ou plutôt des caches d'eZ publish . Ce cache permet à ce CMS de "distribuer" ces pages très rapidement une fois que ce cache a été généré. eZ publish dispose de plusieurs niveaux de cache et une fois combinés, les pages s'affichent rapidement sans demander beaucoup de ressources . En contre partie, par défaut certaines parties du site ne sont pas mises à jour "en temps" réel ce qui est un comble pour un site dynamique.

Heureusement pour remédier à ce problème, il est possible de configurer la manière dont eZ publish vide son cache grâce à la fonctionnalité SmartCacheClear. Par défaut lors de la publication ou la modification d'un objet dans eZ publish les caches associés à cet objet et à celui de ses parents directs sont vidés. Mais, si comme sur ce site, une autre page utilise ces nouvelles données il faut en informer le CMS.

Cette opération se fait dans le fichier de configuration settings/viewcache.ini et pour plus de facilité il vaut mieux ne modifier (ou créer que les fichiers *.append.php). Voici donc un extrait de mon fichier settings/override/viewcache.ini.append.php :

[ViewCacheSettings]
SmartCacheClear=enabled
 
[weblog]
DependentClassIdentifier[]
DependentClassIdentifier[]=folder
MaxParents=3
ClearCacheMethod[]
ClearCacheMethod[]=object
ClearCacheMethod[]=parent 

Ces quelques lignes indiquent au moteur d'eZ publish que lorsqu'un objet de la classe weblog est publié (ou modifié), il doit vider le cache des objets de classe folder en remontant de 3 niveaux maximum en plus des caches de l'objet publié et de celui de ses noeuds parents. Pour plus de détails/options, il faut se reporter aux commentaires du site settings/viewcache.ini en attendant que ce fichier de configuration soit documenté sur le site officiel.

Et voila, ma page d'accueil est enfin mise à jour lors de la publication de ce billet :)