Hey Brian,
What Ho??
This is a nice surprise.

[a /]

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Brian Lesser
Sent: 09 April 2006 20:20
To: [email protected]
Subject: Re: [Red5] [Red5devs] [Red5commits] [649] lhubbard

Hi John,
Actually Flash Communication Server only offered Flash Remoting. Flash 
Media Server also provides loadVars, XML.sendAndLoad, an XMLSocket class 
for setting up persistent connections, and a WebService class to call 
Web Services without Remoting. There is also an XMLStreams class for 
streaming XML over an XMLSocket.
I'm looking forward to seeing your presentation at Flash in the Can.
Cheers,
-Brian

John Grden wrote:

>Luke's right - with  FCS/FMS, if you wanted to get to a database, you can't
>use objects like loadVars or XML.load() on the server side.  You have to
use
>remoting.  With Red5, that restriction doesn't exist.  If you need to talk
>to a db, do it right there in your application with Red5.  Remoting would
be
>used for sending data objects to the client or for another server to
>communicate/look at your data on the red5 server etc.
>
>Does that help?
>
>On 4/9/06, Luke Hubbard ([EMAIL PROTECTED]) <[EMAIL PROTECTED]>
wrote:
>  
>
>>Ok, I think I understand what people want. To be able to call remoting on
>>another server. Thats a bit of a FMS hoop developers had to jump through
to
>>do things like connect to a database or preform some authentication I
think.
>>Since red5 is built on spring, and has remoting built in you dont need to
>>use two servers. Infact I would advise against it. You can just use red5 +
>>hibernate or jdbc. There is still a use case for wanting to talk to
another
>>server via remoting, rtmp etc. I would call that client classes. They have
>>not been built yet, but we do have the protocol codecs, so it should not
be
>>that hard. Expect to see them around 0.6 - 0.7.
>>
>>The tentative date for the release of 0.4 is, around the end of next week,
>>perhaps the monday 17th. We are building back up the features using the
new
>>api. So far things are fitting together nicely. One thing to note is that
>>streaming wont be improved yet, we are just porting the old code to work
>>with the new api. So the memory leak, which I havent had time to check
might
>>still be there. I saw Joachim say that if you remove the codec buffers in
>>the xml it will fix the memory problem. I may be wrong though. We will be
>>focusing on new streaming design for 0.5, steven is taking the lead.
>>
>>-- Luke
>>    
>>


-- 
______________________________________________________________________
Brian Lesser
Assistant Director, Teaching and Technology Support
Computing and Communications Services
Ryerson University
350 Victoria St.
Toronto, Ontario                   Phone: (416) 979-5000 ext. 6835
M5B 2K3                            Fax: (416) 979-5220
Office: AB48D                      E-mail: [EMAIL PROTECTED]
(Enter through LB66)               Web: http://www.ryerson.ca/~blesser
______________________________________________________________________


_______________________________________________
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

Reply via email to