jwright@cs.iastate.edu (Jim Wright) (12/21/89)
So, with a little fast talking I got my way, and a new Appleshare over Ethernet network is on its way to my lab. All fine and dandy, except now I have to worry about network compatibility in my software. I've been reading the file services chapter of IM-V, and it has some good advice. But I want more. What should I look out for? How should I go about making my stuff Appleshare compatible? My programs only need to exist on the server, and update files on the server. They will be run from a diskless workstation. There will only be one copy of the program active at a time, and the data files will only be accessed by one station at a time. (It's all tied to specialized hardware interfaces, so sharing isn't an issue.) Can you recommend a good book/reference on this issue? Does any sample code exist which addresses this? Also, how do I go about arguing with another developer to get them to make their program Appleshare compatible (in the limited sense given above)? They charge $2000 for an application to control one piece of lab equipment (software only), and use "dongle" copy protection. I feel that for that amount of money, we have a right to ask for this. How have others gone about getting this done? Thanks. Jim Wright jwright@atanasoff.cs.iastate.edu -- Jim Wright jwright@atanasoff.cs.iastate.edu