Cómo este post no tendría mucho chiste escribirlo en inglés (y creo que es el primero que escribo en español, claro, no significa que realmente escriba mucho), me permito utilizar mi espacio de ideas aleatorias (llámese blog)¡ para hacer un anuncio:

El sitio de Perl en Español y un servidor les extiende una cordial invitación para asistir al seminario de Perl Básico que se llevará a cabo los días 12-14 de Mayo del presente año (si, los 3 días son de seminario) en la Ciudad de México, en las instalaciones de la CANIETI Sur.

El seminario es teórico-práctico y será impartido por Uriel Lizama (autor de Perl en Español) y su servidor. El principal objetivo es presentar una introducción completa y amena al lenguaje, así como proveer de las herramientas y técnicas necesarias para comenzar a desarrollar aplicaciones de uso múltiple y con esto brindarte la confianza de mezclar dichos conocimientos con alguna otra tecnología.

La información completa del seminario, datos, costos y temario se encuentran en la haciendo click a la imagen que aparece en la parte de arriba.

Saludos.

Definitely.... I don't make honors to the word "blogger". It's been more than 6 months since my last post and, as expected, lots of things happened while time was passing by (and of course I forgot about the blog).

Let's see where to start... First of all, and maybe the most important and noteworthy event is.... that I'm getting married next year!. Yeah... after all, life with Dafne is all fun and nifty. A very productive, interesting and learning experience was acquired by those seven years of amazing relationship that needed to take us to a different landscape, a different challenge and of course, a whole different adventure. So... about that, everything is going smooth; planning, wishing and why not? dreaming.

On the other hand, I've been very busy (fortunately) at work. I'm getting more involved in it day by day, improving certain aspects/components of the project, proposing design ideas and best practices and learning all about the business within.

However, my personal projects didn't get my attention appropriately, they were set on-hold for a very big period of time, but this year (yeah.... right), hopefully, I will continue where I was left.

In fact... I've been working in other projects, mostly related to my work. I wrote a nice JDBC framework (Java) based mostly on Spring's JDBC model, integrating some design patterns like Abstract Factory, Factory method, Template pattern and Façade.

What about Net::RMI? Well... fortunately it is almost finished. Implementation is done, testing is almost done and the only thing left is documentation. Yeah, I need to document every user-land class and write more examples for it. I really hope to put it online very soon, so it will be available through CPAN.

Since I tend to procrastinate (often)... my mind likes to put challenges on me. Last time I was thinking about the idea of writing a series of small articles about design pattern implementations, in at least, the languages I like (ex. Perl and Java). Considering something like drawbacks, pros, implementation issues, design overview and of course: code. All of this, with my very very humble point of view and sense of "where is this useful".

At the end, we have a whole year in front of us again, I will try to make a good use of it, and, putting all my efforts, I'll try to make all those promises and wishes become true.

Until then.... cya.

It's been a while since my last post (again), I have been very busy at work and playing with some Java EE stuff lately. However, I enjoy sharing some of my free time to my personal and open source projects.

A week ago, I just gave a speech about Unix Systems Programming, Chapter 3 - Working with files for the Open Source Community at work. It was practically a two-hour technical discussion on how a Unix-like system sees/handles files and a general overview of syscalls, user-level calls and other topics like the multipurpose fcntl syscall and memory mapped I/O. It was quite fun.

The other side of the story is about Net::RMI, my pure-Perl Remote Method Invocation implementation. Yes, the project is going quite slow, but the design and implementation is near to its final release. While coding the first version of the API, I discovered some design flaws that made me rethink the way the server part was doing its job and also rethink the request-response interchange between the proxy object and the server object.

Here's the UML diagram for the second draft:

As you can see, there are several changes to the API compared to the new version, new classes and a whole new idea on how stuff works internally, In the end, for the user it needs to be transparent.

There's a bad symbol usage in the diagram, the prmiregistry, since this is a class diagram and prmiregistry is not a class, is an independent daemon that waits for requests from the Net::RMI::Registry class. But I wanted to use it to remember that Net::RMI::Registry depends on that process.

Well, we will see what happens, I really hope to finish this stuff as fast as I can, provide a complete test suite and some code examples for the public release.

Until then, have fun.