I'm pretty new to OC but really enjoying it so far.
I've been writing simple robot automation programs and they work out well for me I have trouble grasping some of the more OS related features such as signals/events and the way I can implement services/daemons.
I am implementing a simple network protocol in which servers acting as routers and other computers send packets back and forth to build ARP-like address tables, my end goal being a simplified IP system that routes packets efficiently through a large network using conventional format IPv4 addresses and DNS servers.
Essentially, here is my challenge:
I want to have my computer listen and answer modem signals while not disrupting/stopping an active program or the shell. So I have a few questions to ask.
1) What is the best way to do this?
2) Information is very hard to just come by, I have read a lot about listening to events and then using callback functions, but how does that work outside of an actual program?
3)I read in the API documentation about events, that "Driver Mode" was a way to possibly run listeners alongside the shell but no further information is available about this. What does driver mode refer to?
4) What is the RC API, and how/what does it actually do? It is pretty weakly documented and it almost looks like it is what I need if we are talking about Daemons running along side other programs or the shell.
Essentially, a background process. I do understand that, technically, without true parallel processing, the callbacks will need to finish before the computer will be usable again (I think) but my callbacks are intended to be very short quick message replies or quick file writes.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Hello everyone.
I'm pretty new to OC but really enjoying it so far.
I've been writing simple robot automation programs and they work out well for me I have trouble grasping some of the more OS related features such as signals/events and the way I can implement services/daemons.
I am implementing a simple network protocol in which servers acting as routers and other computers send packets back and forth to build ARP-like address tables, my end goal being a simplified IP system that routes packets efficiently through a large network using conventional format IPv4 addresses and DNS servers.
Essentially, here is my challenge:
I want to have my computer listen and answer modem signals while not disrupting/stopping an active program or the shell. So I have a few questions to ask.
1) What is the best way to do this?
2) Information is very hard to just come by, I have read a lot about listening to events and then using callback functions, but how does that work outside of an actual program?
3)I read in the API documentation about events, that "Driver Mode" was a way to possibly run listeners alongside the shell but no further information is available about this. What does driver mode refer to?
4) What is the RC API, and how/what does it actually do? It is pretty weakly documented and it almost looks like it is what I need if we are talking about Daemons running along side other programs or the shell.
Essentially, a background process. I do understand that, technically, without true parallel processing, the callbacks will need to finish before the computer will be usable again (I think) but my callbacks are intended to be very short quick message replies or quick file writes.
I appreciate any help! Thanks!
Link to post
Share on other sites