Hi All, I am running some tests with Rave and I find it very interesting.
I was wondering about how Rave handles users/account. My understanding is that Rave is a standalone portal, you create an account and then login and manage your widgets. Is my assumption correct? I would propose a use case where Rave is a portal that sits on top of another application and therefore the accounts are uploaded and not created by a user. Such uploading could happen in different ways. 1. One way would be an LDAP connector with LDAP bind authentication and the ability to upload profile data from LDAP. 2. Another way would be openID where you authenticate against an existing application that is an openID provider. You then want to build an ability to add a plugin that connects into a proprietary REST API to upload profile data (i.e. when a user logs in for the first time using openID, the account in Rave is automatically created and the profile data uploaded). Once the account exists you have to be able to sync profile changes both ways. Another question is related to the database used by Rave. I noticed that currently MySQL is used as database. I was wondering what do you think about using a NoSQL DB with Rave? I think this would give Rave better scale and the possibility for redundancy. Thanks, Ioan
