|Subject||Re: FB 1.5 and client connection|
> Adam,Yes and no,
> Would this work for multiple users running the same app that resides on
> a PC in a peer-to-peer network?
> This single PC would also be the FB server.
It does work, we used to implement our software that way, but we found
that the network speeds were causing performance degradation as the
software grows (scope creep).
Our current model consists of a single application and ini file. The
ini file has the location of the "master" binaries, and a relatively
simple program checks the file date of the binaries in the master
folder and downloads them if they are different. The program then
launches the Login screen.
This approach avoids lock conflicts when upgrading binaries, most of
the time no user is using the master directory (except for a second
when they log in), so even if they don't quit, you can still copy the
files into the master directory, and the next time they launch they
If your software is small enough and your networks stable enough to
launch over a share, then I don't see why it would not work (it isn't
hard to test it yourself though).