Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Okay, let heat a bit down, i think the topic is getting too hot now :-) I am not talking about synchronzing two cvs server 24/7 over dial up. The case I mentioned is real and in real business you are faced with such problems (believe it or not, even in germany you don't have DSL everywhere, infact in some areas here DLS is rare and the exception) Or imagne your company (or the other supplier) does only offer dialup (for some security reason or whatever), so this is fact and you can not easy change this. Or the company does not want to give sources outside to a server host company because of some reason... So what is your advice here ? I think Arthur mentioned some add ons to CVSNT for commercial customers. What IS this kind of add on ? Can you share this information or is it secret ? I can think of some file sync software (such as sure synch or similar) kind regards, Bernhard. Tony Hoyle wrote: > Gerhard Fiedler wrote: > >> I'm not really sure where you are going with this. Did you read my last >> message? I wrote about a team in a place without broadband. Not a company >> not signing up for broadband because of bean counting, but a team living >> and working in a place without broadband access available. Believe it or >> not, this is reality, no matter what any telecom statistics say. > > > A team being paid to outsource development for you has the same > considerations as a company no matter what they call themselves. > > You're talking about synchronising two cvs servers 24/7 between > development teams over dialup - what I'm saying is that it's doomed to > failure from the start, because dialup simply is not practical for that > kind of work. > > Stick to one server hosted on a proper server (possibly in the US if you > don't have local hosting companies), and have the developers dialup when > they need to commit if they really are stuck on such slow links, so > you're not dragging down the entire development process to the speed of > the slowest developer. > > Tony