Dan and Cosmin, Here's the situation... I have red5 running on a separate server and my web application and database is on a different server. I'd prefer not to use Red5 with a database. I'd prefer to use a Flash widget to report, using a POST, that something was recorded. This cuts down on the traffic between my servers. Something like this...
1) User loads up the page with record widget 2) User presses record, widget contacts red5 server and starts storing the sound 3) User presses stop and flash widget sends a POST to the web app server and web app server saves the filename etc to the database. Is anything wrong with this? Also, are there any examples that would tell me how to catch the stop recording event from the Red5 and send it to my web app server? I think this is what you both have been suggesting. I'm new to Red5 and don't know how to do that exactly... I have managed to record with default red5 app. Thanks! Mel On 7/13/07, Dan Rossi <[EMAIL PROTECTED]> wrote: > I havent done anything with db stuff yet. But I may plan to integrate > hibernate as an embedded db system for anonymous security authentication > stuff with clients. > > [EMAIL PROTECTED] wrote: > > Yes, I try to limit the red5 interaction to only what it does best. > > But only recently I dug into the server side ( java dev and stuff ) so my > > perspective is somewhat limited. Actually at this point I am amazed by the > > complex communication between flash and red5. As soon as I get to doing > > some DB interaction from my red5 App I'll probably push everything trough > > red5 :) > > > > cosmin > > > > > >> [EMAIL PROTECTED] wrote: > >> > >>> 2. start recording using red5 and use the uid for the recorded file > >>> name. > >>> 3. get record end and success eventts from red5 and at that point call > >>> php > >>> to enter new the filename and other details you grab from the client to > >>> the DB. > >>> > >>> > >> Do you mean a http request to a php script ? That could work aswell but > >> removing that step by adding straight to the database via red5 was my > >> idea. And I guess a uid to generate the stream name first is a good idea. > >> > >> > >> _______________________________________________ > >> Red5 mailing list > >> [email protected] > >> http://osflash.org/mailman/listinfo/red5_osflash.org > >> > >> > > > > > > _______________________________________________ > > Red5 mailing list > > [email protected] > > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > > > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
