CSLA 2.0 'no physical tier' implementation

Zoreloth posted on Thursday, November 02, 2006

I'm developing a particular set of business objects with CSLA 2.0 that will only (and I do mean only) be ever implemented in a client/server architecture. This is because my application integrates with a third party application via an API. Most of my DP methods have API calls, and some have both API calls and SQL. The API calls are to the third party application (which must be executing on the same workstation as my application in order for the API calls to function). I'm wondering if there are things I can do (such as not use the serializable attribute, or use the RunLocal attribute for all dp methods, etc...) to maximize CSLA performance since this particular *logical* business layer will absolutely never be on a different *physical* tier than the UI and will always be "local". Or, should I not even worry about it?

Bayu replied on Thursday, November 02, 2006

Don't worry about it.

Bayu

guyroch replied on Thursday, November 02, 2006

Same here.  When you're using the 'SimpleDataPortal' everything runs local anyway.  And if you look deep in the Csla code base you'll notice that when you app is configured as such it won't tax you with the overhead of serialization.  The framework is _intelligent_ enough not to serialize when not necessary.

Best regards,

Zoreloth replied on Friday, November 03, 2006

Thanks again gents!