Bug 364 – how do I know if Socket::SetSendCallback works ?

Bug 364 - how do I know if Socket::SetSendCallback works ?


Summary:	how do I know if Socket::SetSendCallback works ?

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	network
Version:	pre-release
Hardware:	All All

Importance:	P3 normal
Assigned To:	Craig Dowell

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-09-23 16:31 UTC by Mathieu Lacage
Modified:	2008-10-27 12:59 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
proposed patch (1.06 KB, patch) 2008-10-20 03:30 UTC, Mathieu Lacage	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mathieu Lacage 2008-09-23 16:31:11 UTC

that callback will be inoperative on udp sockets. How do I know this ?

Comment 1 Gustavo J. A. M. Carneiro 2008-09-24 07:23:28 UTC

Socket::SetSendCallback should be functional for UDP sockets IMHO.  Why would it be hard to implement for UDP sockets?  If the implementation knows no better, just call this callback unconditionally after each Send () (preferably via Simulator::Schedule to avoid recursion).

Comment 2 Tom Henderson 2008-09-25 09:33:27 UTC

I agree with Gustavo and seem to recall we discussed and agreed on this behavior back when the socket API was redone.

Comment 3 Mathieu Lacage 2008-10-20 03:30:45 UTC

Created attachment 270 [details]
proposed patch

Comment 4 Rajib Bhattacharjea 2008-10-27 12:59:19 UTC

changeset 362d7e1c12a6