Forums

Hi there,

is there a way to make sure the generic reflector is not used in a client/server scenario? Of course I'm trying to deploy all needed dlls, but I also try to constrain myself to the actual data model, instead of pushing everything to the server. Or would you simply deploy all dlls?

What do you think?

Chris

Well I think the most elegant and also quite simple approach is this:

Create a assembly which contains your all your persisted classes. And then use this assembly on the server and the client. However versioning can be a problem. When to client and server have different versions of the assembly with different classes it may produce strange effects.

From what I understand, one should always supply the model assembly to the server for performance reasons, right?

Now the trouble is to create the assembly which contains all persisted classes. The project is quite complex and I might keep a reference to some object (that probably should not be stored) which is not part of the data models assemblies. If that happens, I'd like to get some kind of notification... Perhaps I just walk basically everything stored in the DB from time to time and reflect my assemblies to see whether that object type is known in there? That is probably possible, but I was hoping for a simpler solution.

You could listen to Creating events, get the newly stored object from the event args and throw if it's of a Type that you don't expect to be stored.

For a sample of how such a listener is created see Db4objects.Db4o.Tests.CLI1.Events.EventRegistryTestCase in the sources.