On Aug 5, 12:32 pm, Huge <[email protected]> wrote: ... > Due to the fact that workstations running our software must never, > ever be able to be offline, we are forbidden from using a SaaS > architecture for Data Access, thus the P2P network and the rich client > model.
Your argument of preventing an offline mode based on the location of nhibernate holds no water. In either model (centralized app server that exposes data through web services or nhibernate on the client), if I pull the network cable, you can no longer fetch new data or update anything with that app. That is not an offline app. Offline apps have to have the ability to cache data, go offline, update the data, and then synchronize at some later point. Regardless, if you have an app that does not have exclusive write to the database, then 2nd level caching is not a great idea anyway. You'll spend more time and effort notifying of dirty caches than is worth it. By not using 2nd level cache, you'll have less problems with stale data and don't have to implement so much messaging. To your point of assuming that your case isn't special, pay attention to the mailing list (or any other mailing list). 99/100 times when people think they have a unique problem that hasn't been solved, they are wrong. Especially when the framework is as old as nhibernate. Unique cases happen, but they are a rare exception. Yours seems to be a unique case, but only because you are trying to use L2 cache for an architecture it wasn't meant for. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
