A preferred option would be to write your own
UserProvider and AuthProvider which would
allow Messenger to hook directly into your existing
I’‘m not quite sure I’'m following you, are you saying
I should replace the user database completely,
doesn’‘t that mean that I’'d have to have add tables
for the relations between users etc. to my own
You wouldn’‘t really be replacing the user database, rather you’'d have Messenger authenticate against your existing user table. And yes, the easiest thing to do would be to add the Messenger tables to the same database that your existing application uses.
Ideally I would want to have something that works
just like adding users via the Smack API (which I
guess would be something like - connect to
createAccount()) but that only allows my app to add
users, not everyone in the world that happens to find
out the address to my Messenger server.
You could certainly use the Smack API to create and delete accounts as needed, but then you’‘re going to have two user databases with same users in them. A potential problem with keeping two user databaes is what would happen if someone changed their name or password in one of the databases, would you want to keep that data synronized? If so, then you’'d have to create a mechanism for detecting the change and updating the tables properly.
So, you’'ll just have to weight the pros and cons of each approach and go with whichever makes the most sense for you.
Hope that helps,