If you are talking about netwoking for CPRS, then latency is the big issue, far outweighing bandwidth issues. CPRS chatters back and forth to the server, so latency times are multiplied many times over, leading to sluggish responce.
Kevin On 8/11/05, Mike Lieman <[EMAIL PROTECTED]> wrote: > On 8/10/05, Maury Pepper <[EMAIL PROTECTED]> wrote: > > With either, it depends on variables, some known, some not. I > > Generally, I divide the market into "Broadband" and "Everything Else". > > Within the broadband, it's all pretty much the same, once it's in and > stable. At that point, the biggest difference is the level of > incompetence in the support organizations. > > "We'll get out there next week" doesn't cut it for a business class > account, and getting results then becomes an issue of "Bad Cop/Crazy > Cop"... > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
