Comments (5)
Yeah, +1 for consistency! I suppose it's a contentious topic, but in line with how standard libraries work, I typically only handle internal errors in my libraries (and perhaps debug logging at most). This leaves the user of the library to implement API-level error handling and logging at large, making it streamlined with the rest of their application.
from coap.
AS the README says this package is a port of the C# .NET project CoAP .NET so it pretty much follows what that did, if it threw an exception we will, if it logged we will etc. There are some differences caused by dart not supporting exactly what .NET does but in the main it should do the same.
If your asking is there an overall strategy of when we throw, log or retry then no.
from coap.
If your asking is there an overall strategy of when we throw, log or retry then no.
is there any chance this could be improved? Would you accept a PR for that, after discussing how things could look like?
from coap.
Yes no problem. One large improvement would to be consistent in what we do across the whole package.
from coap.
Believe this has been addressed. Package re released at version 5.0.0.
from coap.
Related Issues (20)
- Multicast requests using blockwise currently not working HOT 6
- Method not allowed with post request HOT 6
- Since version 4.2.0 observe non confirmable not working properly HOT 13
- Killing network during requests causes uncatchable exception
- Remove Coap prefix from internal classes HOT 1
- Support OSCORE
- Add funding links to package HOT 1
- Planning of next releases HOT 24
- Problem with error handling on timeout or cancel HOT 8
- Address TODO comments across the code base
- Example tdls HOT 36
- openssl (dtls) messages are not processed HOT 15
- Behaviour of observe in case of lost connection HOT 4
- Unhandled Exception when connection is lost HOT 17
- Pure dart dtls HOT 1
- Update to Dart 3 HOT 1
- Slight tweak proposal to Uri handling HOT 1
- Fix static analysis errors introduced by lint 3.0.0 HOT 1
- Investigate why pub thinks the repo and homepage url's in the pubspec.yaml don't exist HOT 1
- Response ETags HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from coap.