With the arrival of the ready-to-use, easy-to-implement AJAX frameworks web sites reworked their concept. From being simple web pages turned into real applications. No matter what the problem is.

Contact databases are easily made unmanageable. They tend to grow in an unordered manner and carry those defects inherent to non categorized huge databases. Users might be able to see the whole database or may end up creating contact duplicates. As long as contacts database is attached to web users database, privacy isn't satisfied. Anyone seeing contacts sees users, maybe even permissions, roles and the like. But how to avoid it? Giving yourself each customer, provider, collaborator and so on, its permissions? Certainly not.

Here is where Social Groups comes in help. Build upon BrightSide Contacts, Social Groups define the way a contact has to be categorized, to those has to be related and which permissions is allowed. Social Groups make a clear vision of Contacts database.

I have been disconnected  from this site quite long. It seems that time isn't working the right way with me. You know, the more I'm supposed to understand the more complicated to write about it. Well, this time I made a break and gathered myself in order to put my two cents saying something about Zkoss.

First, I would like you to notice that this goes about web application frameworks. Java Server Faces, Flex, Google Web Toolkit, Wicket and those of that kind. I have stressed most of them in my way of being productive writing web applications. Difficult, let me tell you.

I love Java, from the very beginning. It happened as much like with C++, one gave me computer control, the other offered the world. That's what Java was all about, being able to be everywhere. Today things had come bigger and Java isn't anymore the applet programing language, but a whole set of APIs to create almost anything.

You could call that the good and the bad of Java. Will depend on who you believe in and where Sun goes to.

Earlier 2005 I had the need to install web statistics for Tomcat web servers. The reason might be obvious: XMLPortal runs on JSP/Servlet containers. Usually, Java hosting plans use Apache server to generate access logs and then redirect requests to Tomcat. This runs pretty well, but once a hosting provider offers to improve your account by sending requests directly to Tomcat, you can't say no. And I said yes. Soon I start missing things, like web statistics. This is how, step by step, I dealt with it. Today I have splendid AWStats on my web site!