Hi,
I know you can use server side extensions to access a database but I think it would be nice if SmartFox Pro would be more database centric. For example if the setUserVariables(), getUserVariables(), setRoomVariables(), getRoomVariables() and the buddyList methods from the Flash api would save and get the data from a database instead of a disk on the server. Also it would be nice when you enter a room ,and get a list of all user Objects, it would automatically get the user objects variables from the database. In addition login and registration methods that accessed the database would be useful.
Bill
database centric
Nice suggestion 
I think we could add this option but not force everyone to use a database as this might be an obstacle for those who don't need it.
Another option we're taking into account is to provide an embedded SQL database engine to SmartFoxServer so that all system and user persistent data can could be stored there. This would also make the server more stand-alone as you ouldn't need to setup your external DB.

I think we could add this option but not force everyone to use a database as this might be an obstacle for those who don't need it.
Another option we're taking into account is to provide an embedded SQL database engine to SmartFoxServer so that all system and user persistent data can could be stored there. This would also make the server more stand-alone as you ouldn't need to setup your external DB.
An embedded sql database engine is an interesting idea. Having the database external would allow you to have it on a seperate machine and spread the load a little bit right? Also having the database seperate would allow you to use it for other purposes or perhaps different applications using the same database. What would some of the advantages of using an embedded database engine be?
Not necessarily. If the database is embedded it means that it's part of the software so you won't be able to split it. Actually running the server and DB on the same machine can be a convenient setup for many small to medium-large applicationsHaving the database external would allow you to have it on a seperate machine and spread the load a little bit right?
When things start to get bigger then it will definately be better to separate the DB from the socket server.
Some of the advantages are:
- easier setup
- faster server -> db communication
- better integration
- the ability to keep all the persistent data in on place only allowing simpler backups etc...