Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
Client SocketException: Socket closed
My simple ThingspeakClass works fine, but after each data upload I:ve got a Client SocketException: Socket closed in the console. Data are continiously transferred to Thingspeak without an further issues.
https://github.com/f41ardu/Thinkspeak-Processing
After implementation of my own web server with a simple POST API using Phyton on a Raspberry data are transferred into my server, but same result. Client SocketException: Socket closed still shows up in the console window after each upload.
Bug or feature?
Works for weeks now on Thingspeak, so I guess it is a issue of the processing.net.*; implementation ?
Tagged: