note monsieur_champs <blockquote>Be sure to ask him to submit all requests as UML diagrams, in triplicate, with TPS cover sheets and circles and arrows and a diagram on the back of each one.</blockquote> Thanks for the recommendation. I'm really well-served on bureaucracy, believe me. The client have a CMM L2 certification and all projects must fulfill a lot of bureaucratic requirements. :-( <blockquote>On the other hand, if you want to keep your job, maybe digging a little deeper is the way to go here. Maybe your architect knows what he's doing. Maybe he has solid, concrete reasons for asking you to do this.</blockquote> Not really. He have a Java based mindset, just that. It's not his fault, he actually works with Java. [perrin] and [izut] arguments are enough to convince him about the non-need of VOs for implement a good DAO in Perl. <blockquote>The [http://www.javaworld.com/javaworld/jw-09-2000/jw-0915-lucene.html|Lucene] and [http://search.cpan.org/dist/Plucene|Plucene] examples</blockquote> Thanks for those. They were nice and very illustrative. It started to show the light to my poor architect. :-) May the [gods] [bless] you for this example and him for accepting it as a good starting point. <blockquote>And the Java guys would rightfully snear and make posts very similar to yours.</blockquote> Oh, please! I'm not sneaking. I'm posting this with the agreement of my architect. We are good friends, and both of us are having fun with this project. :-) BTW, thank you very much for you point of view, it was quite useful. And thanks to [perrin] and [izut] for pointing good solutions for avoid extra coding and still having high quality Perl code.  <div class="pmsig"><div class="pmsig-260843"> -- [monsieur_champs] </div></div> 482728 482740