Hi Karl, I was looking at prevayler but I can not make any assumptions on how many objects / data a person using the server wants to store. Imagine a usecase like google mail. google mail is based on gdata and stores a lot of data I guess. If you combine your mail server like JAMES (I did that to create a frontend for james) with gdata server you could end up with a shit load of data within a day. I can definitely can build some caches inside the storage or cache on the response layer but first I need a "standard" persistence for the server which can scale on many servers as well but single server environment is also desirable at the moment.
best regards simon On 11/22/06, karl wettin <[EMAIL PROTECTED]> wrote:
22 nov 2006 kl. 11.38 skrev Simon Willnauer: > I'm actually looking for alternatives and suggestions How much data is it that you store? I'm using Prevayler with great success in many projects. Hobby and commercial. In some cases I use it as a transactional layer for the index I keep bugging the forum about. In fact, that index is based on the Prevayler hypothesis: all business objects fits in memory. So it consumes quite a bit of RAM. However, the petshop implementation with Prevayler have some 3000 times faster persistency access than an implementation with MySQL (running in memory on the same computer). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
