It isn't clear why you are considering using Flex or what it is you are trying to accomplish. Maybe rephrase your question to make it more targeted.
Your primary question seems to be how to transfer data, with data being in the form of images, sounds, and videos. These would be more accurately classified as "resources" instead of "data." You generally wouldn't store these file types in a database or deliver them via the methods you are asking about. Have your read any Flex books yet? -Mike Chabot On Sat, Nov 1, 2008 at 10:21 AM, spinglittery <[EMAIL PROTECTED]> wrote: > My first post on this marvellous but bewildering resource... > I am a designer/art director heading in the direction of development - and I > am presently > baffled by the number of varieties of possible data transfer, and don't know > what to use. > Almost all the data that I wish to display is visual or audio - print work, > video, some sound > production - and I don't know whether I should be storing my data in a mysql > database > and uploading it via AMFphp, Zend, Weborb or somesuch - or loading it from > an external > xml file and image/video/thumbnail folders. I would like to have optimum > conditions for > viewing the work at a good size without pixillation, but of course I want it > to be fast > enough to retain attention. > Should I use modules to separate the image gallery from the video material? > Would a framework help me? > Would I be better off remaining in pure flash, avoiding the added Flex > overhead? > Or is there a way with actionscripted components of reducing and > streamlining...? > Would I be best off using HTTPService, Remote Object, Webservice, or > NetConnection > classes for my remote transfers? ( All my material can reside in the same > domain...) > > There are so many amazing alternatives out there, I am spoiled for choice, > and sometimes > disappointed by the result after I have set everything up and compiled. > Which may be my > naivity in some area, rather than a problem with the method as a whole. > I have made several stabs at using various open source and Adobe tutorial > solutions - for > instance, I rebuilt Video Jukebox only to find that the file size made it > all far too > cumbersome to be workable anywhere but locally... I would like the .flv's - > varying from > 15 to 180 seconds in length - to look respectable at 50% screen size, but > this means many > video players become sluggish. Is it because I am not using the best way of > loading the > data? > I would be very happy if someone could give me some pointers. > > p.s: I can't afford to use Live Cycle/Cold fusion options - but should I be > looking into > Blaze DS, or Red 5, or is that overegging it for my needs? I won't have lots > of dynamic > data updates - but perhaps streaming is a big improvement on progressive? > Wish I > knew... > >
