I don't have the details, but my dad did something similar to what you want, across an 8 mile span, and it works very reliably. In his case, he had clear line of sight due to being up on a hill and shooting to an access point he set up at a friends in the valley. He used a zzyyx router (cheap, has a bridge mode, and great support) at his end, some generic linksys or such at the other end, and a couple of directional antennas (dont remember the exact specs). Took a bit of tinkering to set up, but he gets better throughput than my cheaper DSL.
NeXTstep utilized a very similar sounding packaged application directory approach. There, if you "ran" a directory named "XXX.app", it ran the executable within that directory named "XXX".
I was just discoving xnix, so I don't remember all of the details, but I believe it used static libs, and depending on how you manipulated a.app it worked like a directory or as a unit. Putting the parent directory of XXX.app in the path allowed execution of the program.
It did work quite well, and I found the idea very effective compared to Windoze, Dos, and SunOS approaches. You could just drag a package around, and the file compartmentalization was quite a step forward. I eventually hacked a similar capability under Dos using 4dos and executable extensions.
Slashdot Mirror
... on Facebook. HeHeHe .... HeHe .... He .. He .. hmmm???
I don't have the details, but my dad did something similar to what you want, across an 8 mile span, and it works very reliably. In his case, he had clear line of sight due to being up on a hill and shooting to an access point he set up at a friends in the valley. He used a zzyyx router (cheap, has a bridge mode, and great support) at his end, some generic linksys or such at the other end, and a couple of directional antennas (dont remember the exact specs). Took a bit of tinkering to set up, but he gets better throughput than my cheaper DSL.
NeXTstep utilized a very similar sounding packaged application directory approach. There, if you "ran" a directory named "XXX.app", it ran the executable within that directory named "XXX". I was just discoving xnix, so I don't remember all of the details, but I believe it used static libs, and depending on how you manipulated a .app it worked like a directory or as a unit. Putting the parent directory of XXX.app in the path allowed execution of the program.
It did work quite well, and I found the idea very effective compared to Windoze, Dos, and SunOS approaches. You could just drag a package around, and the file compartmentalization was quite a step forward. I eventually hacked a similar capability under Dos using 4dos and executable extensions.