Today I’ve decided to freeze jxmpp-bot project. In fact there were tons of good and bad ideas implemented. The huge infrastructure was created. Now it’s time to rewrite project from scratch and here are the reasons.
Today I’ve decided to freeze jxmpp-bot project. In fact there were tons of good and bad ideas implemented. The huge infrastructure was created. Now it’s time to rewrite project from scratch and here are the reasons.
The main feature (sweet one) of jxmpp-bot by design is it’s flexible plugin-oriented architecture. Any functionality can be added using plugins. In this post about the architecture overview I’ve mentioned PluginManager. Now it’s time to make a more detailed review.
It’s time to analyze requirements (5) and (7) from the requirements list
Now when XMPP subsystem is designed and implementation is ready and polished I’d like to share some my ideas.
We already have Permissions service which is responsible for managing user jabber identifiers. Now lets talk about Visits service.
It’s been a while since I’ve posted about jxmpp-bot project.
In this post I’d like to talk about composition and inheritance on practical example.
Read the rest of this entry »
Today let’s talk about User Management use-cases more closely. We need several database mappers, several services and facade pattern.