Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Print
Author Topic: Server Interface  (Read 8491 times)
gabon
Jr. Member
**
Posts: 14


View Profile Email
« 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
Logged
puremvc
Global Moderator
Hero Member
*****
Posts: 2871



View Profile WWW Email
« Reply #1 on: March 09, 2008, 07:27:47 »

Try using a business delegate. Have a look at the CafeTownsend demo for this.

-=Cliff>
Logged
gabon
Jr. Member
**
Posts: 14


View Profile Email
« Reply #2 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
Logged
Joel Hooks
Courseware Beta
Sr. Member
***
Posts: 146


baby steps

 - 46288188  - passport@provinsal.com  - joeltuff
View Profile WWW Email
« Reply #3 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.
Logged

http://joelhooks.com - my ramblings about developing with actionscript and python using pureMVC and django respectively.
Pages: [1]
Print