byteoflogic 0 Posted July 14, 2016 Share Posted July 14, 2016 I think this is what this forum is for? I don't really have any authority on this, but thought it would make sense if everyone used the same ports for this sort of functionality. I would suggest using, say, port 10 (doesn't really matter) for all messages containing lua to execute, and putting said lua in the last part of the packet: (modem.broadcast(10, "username", "password", "gpu.set(0, 0, \"Hello World\")")) Why is this useful? I can now have a single drone that works with many different programs with no real configuration. I can download programs via oppm, or paste them in from the internet, and they will always use the same port to access said functionality. Quote Link to post Share on other sites
GreaseMonkey 7 Posted August 1, 2016 Share Posted August 1, 2016 My understanding is that this forum is mostly for putting proposed standards and whatnot but it should be fine for fleshing out ideas for standards. The problem with this approach of course is you're basically sending a password in the clear. But having a standard protocol + port would be nice. I'd personally do away with the username+password scheme and instead just check if the sender is on a list of authorised IDs. Having session logic should not be necessary as if something needs to be returned over the modem, it should be embedded into the code to run. At this point you'd probably want to flesh out a standard API. Probably this: * remexec.auth_add(component_id) * remexec.auth_del(component_id) The calls themselves should be self-explanatory. Namespaces that should be included already: * component * computer * remexec Would something like that work? Quote Link to post Share on other sites