Using GOODS for authentication on a Seaside app
The GOODS database is a nice cross-plaform OO Database, and there is a Squeak client, so here is a usage pattern that I use for login...
The goal is be able to use your domain objects from Seaside and not really know or care that they are in a GOODS database. This means making your session do the work of refreshing the database from the server and commiting any domain objects that change in your app. Having the GOODS db in the session does away with loads of concurrency issues you might have to deal with if you were to have a shared database connection. Since our apps live in Seaside sessions, it's a natural place to house it.
Although this example is related to a login type of use, any change to User objects will also be commited.
