Activity
From 06/29/2016 to 07/28/2016
07/28/2016
- 01:33 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- ... to elaborate my question, suppose an application that receives an OnExpressFailure callback with `TRANSPORT_UNCON...
- 11:05 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- Hi Andrew. You have a good point. Simply reacting to the synchronous call to send is little better than throwing a fa...
07/27/2016
- 02:22 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- Jeff, let's see if I understand: as it looks right now, all we can do is catch the AsyncTcpTransport's IOException in...
07/25/2016
- 01:15 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- Hi Andrew. In branch issue/2075-OnExpressFailure I added expressInterest overloads which take an OnExpressFailure.<br...
07/22/2016
- 02:14 PM Bug #3448 (Closed): Retrieval of data using full name
- Matching on the Data packet full name is not supported. The search through the PIT uses Interest.matchesData:<br>
ht... - 02:05 PM Bug #3447 (Closed): Data.getFullName()
- In all libraries added Data.getFullName. Also added Interest.matchesData and use it when matching and incoming data p...
- 02:03 PM Feature #3450 (Closed): Name.Component API extension: is* methods
- In all libraries, added isGeneric and isImplicitSha256Digest.
- 02:02 PM Feature #3451 (Closed): Name.Component API extension: from* methods
- In all libraries, added fromImplicitSha256Digest.
07/20/2016
- 01:24 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- Makes sense to me.
- 10:51 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- Hi Andrew. The first argument to OnFailure will be the Interest which was passed to expressInterest. Since this callb...
07/18/2016
- 02:08 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- That makes sense; sometimes I forget you have to consider other languages.
- 10:25 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- Glad you like the idea. Unless someone objects, we'll try the approach with Exception subclassing.
One point. Whi... - 09:08 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- I see your point about the OnNack; for the OnFailure, I like the second version better and the Exception-subclassing ...
07/14/2016
- 03:03 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder
- Hi Andrew. I'd like to keep OnNack as its own callback since it's a specific message sent by the network and is part ...
Also available in: Atom