search

DCC-EX / BaseStation-FB

The FireBox version of the CS code moved here so that all new code could be moved into CS-EX
GNU General Public License v3.0
0 stars 0 forks source link

Add callback number syntax to JMRI interface #11

Open davidcutting42 opened 4 years ago

davidcutting42 commented 4 years ago

Currently, if an ESP32 is connected to the CommandStation and multiple JMRI clients over TCP/IP, there is no way for the ESP32 to differentiate which incoming messages are for which client. I already fixed the problem of messages getting sent out to all connected devices, but that doesn't solve this problem fully because the clients are at a deeper level. Need to implement an optional callback number that is wrapped around the existing JMRI/DCC++ tags. Something like [callbacknum<DCC++ tag>]

FrightRisk commented 4 years ago

That might work.

grbba commented 4 years ago

Hello, I don't quite understand the setup described. Tell me if i am right : you have multiple clients connected to the JRMI server and the server is connected to the ESP32 ? The ESP32 therefore has only one connection and has no idea about the original source (client connected to JRMI ) off the incoming traffic ? What you want is a sort of tunnel between the client and the ESP running through the JRMI server ?

dexslab commented 4 years ago

This is highly recommended and should be implemented all around for interfaces as well

ldribin commented 4 years ago

LarryD added this Issue to the Dev Project

Asbelos commented 4 years ago

The ONLY module that should know what to do with the reply is the WifiInterface which is common to all wifi traffic. This should NOT be visible to the routines it calls (DCCEXparser, WiThrottle or HTTP callback) That way madness lies.