One proxy to handle many calls, or many proxies to handle one each?

[jeffyamada]

Ok, so I have a series of related service calls for data. In this instance they're about an "Event" ( as in a conference ). There are xml feeds for things like the "Event Schedule", or "Upcoming Events", or "Hotel/Travel Listings".

All of these feeds are interelated, as they all relate to events, usually a specific one, or in the case of upcoming events, several. What I'm sitting here wondering is if I should have a single proxy handle calls to these feeds, or a proxy per feed.

I think I like the proxy-per feed approach mostly because it allows me to keep the proxies closer to the IProxy signature making them more reusable and easily understood. It also helps encapsulate feed specific actions such as parsing to one domain model per proxy...right?

Anyone have any thoughts?

[puremvc]

If they're different services, I'd definitely go with multiple proxies. Then you can use commands to assemble/cross-relate the data in the view. Or let the proxies know about each other and form their own hierarchies.

-=Cliff>

[jeffyamada]

Awesome! Thanks Cliff!