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.
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.
Today let’s talk about User Management use-cases more closely. We need several database mappers, several services and facade pattern.
Now, when Syslog subsystem is ready it’s time to create user-management subsystem
I’ve implemented SyslogSessionMapper and associated unit tests. So far tests are passed and thats sweet. Not let’s time to continue
