Actions
Task #3101
open
Exception safety of Face::onReceiveElement
Status:
New
Priority:
Normal
Assignee:
-
Category:
Base
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
What is the expected exception safety of Face::onReceiveElement. As of right now, it will throw tlv::Error derived exception any time somebody presents a valid TLV block that looks like Interest, Data (after #2930 like NDNLP) packet, but something is wrong with the packet.
The consequence of this exception (it is not handled, as far as I checked) is that the application will probably crash or stop functioning, as processing loop will be terminated.
Should we change that or it is an intended behavior?
Updated by Junxiao Shi over 8 years ago
- Status changed from Feedback to New
20150814 conference call decides to make the behavior same as NFD UnixStreamFace: bad packets should be ignored silently (or with logging).
Actions