I am not sure we could have BlazeDS equivalent on the apache web site. So maybe text data (info on apps) could be stored in a simple xml file. Even with hundreds of apps it shouldn't be that large. And the images (screenshots) would be available as static resources, as it is today, and loaded on demand by the flex app. AFAIK, javascript can also parse remote XML files, so data storage would be independent of the implementation (js or flex).
WDYT? Maurice -----Message d'origine----- De : Kessler CTR Mark J [mailto:mark.kessler....@usmc.mil] Envoyé : mercredi 18 décembre 2013 12:05 À : dev@flex.apache.org Objet : RE: Flex showcase I like the flex app idea. The question is what do we have in the way of server side to handle dynamic data requests and how are we going to store the data -Mark. -----Original Message----- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Wednesday, December 18, 2013 5:58 AM To: dev@flex.apache.org Subject: RE: Flex showcase >But it does bring up the point of how we are going to organize the page >someday to handle large amounts of entries. - Maybe the showcase itself could be a Flex app, with tags, ranking/votes , comments, etc... - we could split in mobile / desktop (just ideas) Maurice
