|
Bugzilla – Full Text Bug Listing |
| Summary: | Ipv4L4Demux is useful ? | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Mathieu Lacage <mathieu.lacage> |
| Component: | internet | Assignee: | ns-bugs <ns-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | move Ipv4L4Demux functionality to Ipv4L3Protocol. | ||
|
Description
Mathieu Lacage
2008-08-11 17:23:29 UTC
Created attachment 236 [details]
move Ipv4L4Demux functionality to Ipv4L3Protocol.
I am okay with this patch. I think we need to solicit some feedback from George, but I can't seem to add George as a CC... this is because george has no bugzilla account (In reply to comment #2) > I am okay with this patch. I think we need to solicit some feedback from > George, but I can't seem to add George as a CC... > George has an account now, but that was another bug :-) After speaking with him, the utility of it was simply logical separation between layer three, and the interface between layer three and layer four. That said, he doesn't feel strongly enough about this to prevent what you suggest. There are lots of "changes" (which look like they aren't really changes) to the python bindings in this diff...I guess this is a result of running the pybindgen scanner for the updated API? So long as this is the case, please feel free to apply. (In reply to comment #4) > (In reply to comment #2) > > I am okay with this patch. I think we need to solicit some feedback from > > George, but I can't seem to add George as a CC... > > > > George has an account now, but that was another bug :-) > > After speaking with him, the utility of it was simply logical separation > between layer three, and the interface between layer three and layer four. > That said, he doesn't feel strongly enough about this to prevent what you > suggest. > > There are lots of "changes" (which look like they aren't really changes) to the > python bindings in this diff...I guess this is a result of running the > pybindgen scanner for the updated API? So long as this is the case, please > feel free to apply. yes, this is the result of running the scanner. > changeset ad0a36bfdb62 |