[
https://issues.apache.org/jira/browse/LABS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589104#action_12589104
]
Bernd Fondermann commented on LABS-119:
---------------------------------------
> what kind of persistence mechanism did you think of?
up until now, I was kind of avoiding this topic. thank you for bringing it onto
the table :-)
> since there's other data to store (eg. registered users), a database might
> fit in.
right. a relational DB would be a strong choice. preferably Derby.
another option would be a more semi-structured storage, like for example [EMAIL
PROTECTED]
being lesser tied to some schema, this would provide for more flexibility as
other extensions need their own persistence.
but RDB sounds the easiest to start with.
> or do you rather want to store data based on files (eg. per jid)?
rather not. especially since jids can have non-ascii chars. means running into
encoding and all kinds of other issues.
> next question would be: pure jdbc? ibatis? openjpa?
ibatis, openjpa, hibernate, something like this.
what do you think?
BTW, should we move this discussion from jira to [EMAIL PROTECTED]
Bernd
> Implement Roster retrieval and management
> -----------------------------------------
>
> Key: LABS-119
> URL: https://issues.apache.org/jira/browse/LABS-119
> Project: Labs
> Issue Type: New Feature
> Components: Vysper
> Reporter: Bernd Fondermann
>
> Implement the logic specified in RFC3921 chapter 7. The roster is stored on
> the server for each user, so this includes implementing some sort of
> persistence mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
