Comments (4)
that naming stems from the original txthings, which seems to implement some more generic twisted interface. one could argue that the METHOD verbs of both HTTP and CoAP are always uppercased, which forms a prevailing style, but on the other hand we don't have to care much about compatibility yet (no api-stable release has been made, my concern is mainly about doing changes in a way that allows library users to easily migrate, eg. with search/replace).
i'm willing to do that change, but would also accept a pull request; thanks for reporting.
from aiocoap.
No problem. Here is the pull request.
from aiocoap.
cherry-picked and done, thank you.
i've changed two minor things:
- commit messages should have a short single-line description followed by an empty line. (i don't strictly follow the 50 chars limit, but the general formatting has good reasons.
- use
str(x)
instead ofx.__str__()
, avoiding python internals
from aiocoap.
Sounds reasonable, thank you!
from aiocoap.
Related Issues (20)
- GET+observe with new state to trigger some process
- DTLS inclusion of server implementation
- coaps+ws: SSL Context defaults to `None` which make websockets connect through HTTP HOT 6
- pyodide: Prune transports
- How to use port 5683 for both client and server to send and receive device messages HOT 2
- Creating URI for the request without coap scheme HOT 2
- Tests don't cover regular UDP behavior
- Token variable in Message seems to get ignored. HOT 4
- Tradfri: Home Assistant: TypeError("'NoneType' object does not support item assignment") HOT 3
- Specifiy the network interface on windows HOT 3
- Adding Type Annotations and Package Type Information HOT 5
- Keeping DTLS session alive HOT 1
- All appears to be working but no response being delivered HOT 11
- TestServerTCP tests fail garbage collection on 3.12
- How to simultaneously observe multiple resources? HOT 6
- Outdated URL in Readme HOT 1
- Possible to only alert subset of resource observers? HOT 2
- Degraded UX when attempting to interact with non-coap hosts HOT 1
- Network error: [Errno 111] - Cannot interact with CoAP server outside a Docker Container HOT 2
- Drop socknumbers workaround
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 aiocoap.