[FreeNX-kNX] Upcoming release 10/10 and status of redesign

[brendan powers]

Hi,

Is a SQL backend for session data really needed? It would seem that a
simple API for storing session data could be defined, and a backend
could use whatever it needed to store and synchronize the data with
other clients if necessary. I definitely see how a SQL database is
useful when you have load balanced servers that need to share data.
However, it seems a little overkill to store the little but of session
data in a database, and makes setup much more difficult.

I would at least provide an sqllite backend that is set up by default,
so you don't have to worry about it while setting up freenx.

Thats just my $.02, i hope its helpful:)

On 10/1/07, Fabian Franz <FabianFranz at gmx.de> wrote:
> > Could we please allow generalized backend?
> >
> > I am not sure what you are intending to use a full blow relational DB
> > backend for, but do not make it MySQL only.
>
> _Exchangable_ but central session database.
>
> MySQL was just an example, though I agree that only SQL 92 syntax should be used so DB is exchangable and query layer can be written without specific backend in mind.
>
> cu
>
> Fabian
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>