CSLA .NET discussion

Re: Keep object on Server side only

RockfordLhotka — Thu, 23 Feb 2012 02:05:22 GMT

Keep in mind that you can make data portal calls on the server and they will work fine. The real question is hiding behind Jonny's answer- what server code do you have that will call the data portal, and how will you keep the resulting object in memory on the server?

In general, today's server technologies are designed to be stateless and you wil have to devise a way to maintain state in a world not designed to help you.

Re: Keep object on Server side only

JonnyBee — Wed, 22 Feb 2012 17:46:38 GMT

You can have an object that live in a

static class (in your own assembly)
memory cache (System.Runtime.Caching.MemoryCache)
distributed cache (AppFabric)

CSLA does not provide utilities or helper classes for "server side only" objects but not a tricky part to implement or use.

Keep object on Server side only

Pavel — Wed, 22 Feb 2012 15:32:51 GMT

Hi,

The question is how to keep object on Server side without returning it to a client.

I can see that all factory method and DataPortal_XYZ intended to return result to client.

Is there any way to create object to use it during application life without even attempt to return it to client.

I have 3-tier application and both libraries on client and server the same(WinForms).

Thanks,