- From: Andreas Jungmaier <ajung AT exp-math.uni-essen.de>
- To: discussion AT sctp.de, "Sanjeev" <jaya.panem AT mahindrabt.com>
- Subject: Re: [SCTP-Discussion] is it necessary to run the eventLoop to be able to receive any messages
- Date: Tue Feb 19 11:22:01 2002
- List-id: SCTP Discussions <discussion.sctp.de>
- Organization: University Essen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, 19. February 2002 10:35, Sanjeev wrote:
>
Hi!,
>
I have a few questions regarding the way a UA will be able to receive
>
messages from the SCTP.
>
>
1).
>
(a) It is mentioned that if the call back functions are registered, and the
>
eventLoop executed, the corresponding functions are called when something
>
comes to the SCTP. Is it the only way by which the UA can receive a message
>
from the SCTP.
Yes. Thus you get a notification when an event occurrs. What other ways
do you have in mind ?
>
(b) In case, i have multiple applications running ovber a common SCTP
>
layer, will each associationId be having its own eventLoop running?
No, the eventLoop (or getEvent()) functions basically
- - call poll() function to check for read events on the SCTP/Raw-Socket
and user-registered file descriptors.
- - schedule timer events.
for all events of the sctplib. You could consider using threads though,
where the eventloop() would be one thread. The socket API library uses a model
like this.
>
2). Instead of calling the eventLoop, if the UA calls the Receive API of
>
the SCTP, will the message be delivered?
No. You need the event scheduling from either ventLoop() or getEvent()
>
if yes, is the Receive call blocking?
The receive call can be called any time. And doesn't block.
Regards,
Andreas
- --
- ------------------------------------------------------------------------
Dipl.-Ing. Andreas Jungmaier | _
Computer Networking Technology Group | ASCII ribbon campaign ( )
University of Essen | - against HTML email X
http://www.exp-math.uni-essen.de/~ajung | & vcards / \
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see
http://www.gnupg.org
iD8DBQE8ciZWXAsLBNOCSsARAphGAJ4w2PPilGLAa41SNcW/b/eBHu6BKgCggn4T
GF0dZL3lX7GVAsGwm+8DJiE=
=zy5H
-----END PGP SIGNATURE-----
Archive powered by MHonArc 2.6.19+.