|
Title: Server Interface Post by: gabon on March 09, 2008, 05:52:57 In the application I'm doing I've a proxy (singleton) that does all the calls to the server (with weborb and different services). Then I register and unregister commands that observe its events based on the section where I'm. This class of course is growing and I'm wondering if and how I should split it, keeping in mind the reusability of the services.
Thanks, chr Title: Re: Server Interface Post by: puremvc on March 09, 2008, 07:27:47 Try using a business delegate. Have a look at the CafeTownsend demo for this.
-=Cliff> Title: Re: Server Interface Post by: gabon on March 09, 2008, 04:11:19 Quite interesting, in this case the reusable part would be the delegate. I'll give it some thoughts.
Thanks Cliff, chr Title: Re: Server Interface Post by: Joel Hooks on March 09, 2008, 05:29:28 I am doing a similar thing in an application. Originally I had a DataProxy, but it soon grew out of control. Now I divide it by database tables ( ie TaskProxy, EventProxy, PersonProxy ). I have a delegate that I instantiate in each proxy for making calls to that particular table. It gives me nice seperation, and easy to manage classes.
|