[Live-devel] Reception Packet Information

[Dixon Siu]

Understood! Thanks a lot.

Regards,
Dixon

> -----Original Message-----
> From: live-devel-bounces at ns.live.com
> [mailto:live-devel-bounces at ns.live.com]On Behalf Of Ross Finlayson
> Sent: Wednesday, June 23, 2004 9:59 AM
> To: LIVE.COM Streaming Media - development & use
> Subject: RE: [Live-devel] Reception Packet Information
>
>
>
> >The trick is that within getCurrentReceiverPacketInfo(), I
> should do this:
> >{
> >// perform information gathering
> >...
> >// at the end, schedule another task
> >env->taskScheduler().scheduleDelayedTask(n, getCurrentReceiverPacketInfo,
> >data); // this will be executed next
> >}
>
> That's right.
>
> >So it will be recursively executed by doEventLoop every n
> microseconds AND
> >does not affect the live.com's thread. The idea is kind of like
> >doGetNextFrame() in each source reading class, doGetNextFrame()
> perform the
> >reading, then at the very end, there is a scheduleDelayedTask()
> call to loop
> >back.
>
> That's basically correct, except for your use of the word
> "recursively".  There's no recursion going on here.  Note that that when
> your "getCurrentReceiverPacketInfo()" function calls
> "scheduleDelayTask()"
> to schedule another, future, call to "getCurrentReceiverPacketInfo()", it
> doesn't actually call "getCurrentReceiverPacketInfo()" at that
> time.  That
> call doesn't happen until the thread of control returns to the event loop
> ("doEventLoop()").  So, there's no recursive call.
>
>
> 	Ross Finlayson
> 	LIVE.COM
> 	<http://www.live.com/>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live.com
> http://lists.live.com/mailman/listinfo/live-devel
>
>
> __________ NOD32 1.793 (20040622) Information __________
>
> This message was checked by NOD32 Antivirus System.
> http://www.nod32.com
>
>