|
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
|
 |
|
 Show Posts
|
|
Pages: [1]
|
|
2
|
Announcements and General Discussion / General Discussion / Mediator or Proxy
|
on: November 18, 2009, 01:46:16
|
|
I'm writing several methods in javascript to handle the scroll position of very tall flash piece. I'm using PureMVC within flash and am wondering if I should interact with the javascript functions using a Proxy or a Mediator.
My initial instinct was to use a Proxy since it will be setting and getting data, but it occurred to me that none of this data is "model" data, and the scrollbar and browser scroller are actually more UI components.
Any guidance would be hugely appreciated, many thanks in advance!
|
|
|
|
|
4
|
Announcements and General Discussion / Architecture / One proxy to handle many calls, or many proxies to handle one each?
|
on: April 14, 2009, 03:37:11
|
|
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?
|
|
|
|
|
|
|
