|
Thanks Dominick,
The major debug on getting red5 up and running was doing Robert Taylor's videos. They made all the difference actually. I'd been dealing with path problems and this and that, but really it was just the howto and getting the eclipse environment set up with red5. Scopes: That clears it up pretty much, right now I'm just using a single scope through my original context which is my service. So essentially you can make multiple scopes like different sub services? Is there a practical example with this? I guess my train of thought is you connect to one context path and then you're done and then this handles the rest. I'm essentially not using a Scope right now because all I do is connect through the Context. But there must be a default scope for even the context? Like: rtmp://localhost/myapp myapp is the Context path, but it still has a scope associated with it. How does this work? Best, Austin ---------- Original Message ----------- From: "Dominick Accattato" <[EMAIL PROTECTED]> To: [email protected] Sent: Fri, 8 Sep 2006 15:22:26 -0400 Subject: Re: [Red5] Scope and IServiceCapableConnection > Austin: > > Good to see you working through your problems. > > Yes, Scope's Context's can get awful confusing. I'm sure many of us will explain it differently. But heres my take. > > rtmp://<domain>/<context>/<scope> > > so for instance, the application is your context > and scope is your room > > ie: > > rtmp://www.mydomain.com/myApp/room1 > or > rtmp://www.mydomain.com/weatherApp/ny > > and IScope is an interface that you can deal with. Basic scope is transparent through polymorphism. When your dealing with IScope you could be dealing with a Basic scope without even knowing. > > hth > > On 9/8/06, Austin Kottke <[EMAIL PROTECTED]> wrote:
------- End of Original Message ------- |
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
