[WebDNA] The phone home system is undesirable ...
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101672
interpreted = N
texte = > These kinds of erroneous remarks only reveal > more about the person who utters them. Please point out something specific that I said which is erroneous, thanks. > The crashing stuff that was reported had nothing > to do with the "phone home" system. Then what was causing it? Was there "something else" that may have affected so many users at roughly the same time? You'll have to do more than make a claim like this in order to convince me. You were never a part of SmithMicro when this issue was first discussed as a potential problem years ago, and your limited testing on and off for a month after you bought the software is hardly what I would call definitive or conclusive by any stretch of the imagination. And what's the deal with this phone home server of yours anyways? If it's not needed to prevent WebDNA servers around the world from crashing or having other problems then what the heck are you doing still running it? Why don't you just get rid of the damn thing??? Are you running it so you can spy on existing WebDNA users and try to catch them using one license on two or more servers like SmithMicro used to do? Is that what this is all about? This brings up an important issue relating to your company's attitudes with regard to its customers, so let me ask this simple question: Will you remove the phone home code from every new version of WebDNA you release from now on? You know, you don't always have to follow in SmithMicro's footsteps. They never made anything out of the software and it would be nice if you do not repeat their failures and mistakes. I don't know what anyone else thinks about this issue, but I think it's bad karma to include code like this in your software. It does absolutely nothing to make WebDNA better, instead it make it worse by open up the possibility that it might actually create problems. Get rid of it, that's what I say! Sincerely, Ken Grome > >>Other than the dark period of time when there were lots > >>of people crashing due to a lack of phone home server, > >> it has been working perfectly for years. > > > > Steve, > > > > Doesn't it make sense that this may still be the cause > > of the problem? I mean, just because WSC may have its > > own phone home server online now, that doesn't mean it > > is always available, or that the network is always > > available. > > > > I can't believe SmithMicro actually implemented this > > "big brother" system to begin with -- especially when > > the code is so bad that it causes the server to crash > > when it cannot make a connection. To me this is worse > > than anything Microsoft has ever done ... :( > > > > Sincerely, > > Ken Grome > > Ken, > These kinds of erroneous remarks only reveal more about > the person who utters them. > > The crashing stuff that was reported had nothing to do > with the "phone home" system. I did a good month of > behind the scenes testing, and there was no correlation > between the complaints and what we were doing with > enabling/un-enabling (and configuring) of the phone home > system. > > It's so easy to point fingers... it's much harder to > actually learn about Web Serving and managing a server. > > I had some problems with a server I was managing back > about the same time as those reports referenced above. > After I fixed the server config errors, it has run over a > year now (version 6.0a) without a restart. It's running > under the heaviest WebDNA load that I have every worked > with in my 10 years of working with WebDNA and it hasn't > even a hiccup. > > Please watch the accusations.. because this *new* WebDNA > list will not tolerate slanderous remarks. > > Donovan
Associated Messages, from the most recent to the oldest:
> These kinds of erroneous remarks only reveal > more about the person who utters them. Please point out something specific that I said which is erroneous, thanks. > The crashing stuff that was reported had nothing > to do with the "phone home" system. Then what was causing it? Was there "something else" that may have affected so many users at roughly the same time? You'll have to do more than make a claim like this in order to convince me. You were never a part of SmithMicro when this issue was first discussed as a potential problem years ago, and your limited testing on and off for a month after you bought the software is hardly what I would call definitive or conclusive by any stretch of the imagination. And what's the deal with this phone home server of yours anyways? If it's not needed to prevent WebDNA servers around the world from crashing or having other problems then what the heck are you doing still running it? Why don't you just get rid of the damn thing??? Are you running it so you can spy on existing WebDNA users and try to catch them using one license on two or more servers like SmithMicro used to do? Is that what this is all about? This brings up an important issue relating to your company's attitudes with regard to its customers, so let me ask this simple question: Will you remove the phone home code from every new version of WebDNA you release from now on? You know, you don't always have to follow in SmithMicro's footsteps. They never made anything out of the software and it would be nice if you do not repeat their failures and mistakes. I don't know what anyone else thinks about this issue, but I think it's bad karma to include code like this in your software. It does absolutely nothing to make WebDNA better, instead it make it worse by open up the possibility that it might actually create problems. Get rid of it, that's what I say! Sincerely, Ken Grome > >>Other than the dark period of time when there were lots > >>of people crashing due to a lack of phone home server, > >> it has been working perfectly for years. > > > > Steve, > > > > Doesn't it make sense that this may still be the cause > > of the problem? I mean, just because WSC may have its > > own phone home server online now, that doesn't mean it > > is always available, or that the network is always > > available. > > > > I can't believe SmithMicro actually implemented this > > "big brother" system to begin with -- especially when > > the code is so bad that it causes the server to crash > > when it cannot make a connection. To me this is worse > > than anything Microsoft has ever done ... :( > > > > Sincerely, > > Ken Grome > > Ken, > These kinds of erroneous remarks only reveal more about > the person who utters them. > > The crashing stuff that was reported had nothing to do > with the "phone home" system. I did a good month of > behind the scenes testing, and there was no correlation > between the complaints and what we were doing with > enabling/un-enabling (and configuring) of the phone home > system. > > It's so easy to point fingers... it's much harder to > actually learn about Web Serving and managing a server. > > I had some problems with a server I was managing back > about the same time as those reports referenced above. > After I fixed the server config errors, it has run over a > year now (version 6.0a) without a restart. It's running > under the heaviest WebDNA load that I have every worked > with in my 10 years of working with WebDNA and it hasn't > even a hiccup. > > Please watch the accusations.. because this *new* WebDNA > list will not tolerate slanderous remarks. > > Donovan
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
make updates in a temporary database (2004)
file uploads with webcat...binary? (1998)
Latin Characters (1998)
Multiple SSL Keys (1998)
Hiding HTML and page breaks (1997)
Help with sorting search results sorting (1998)
WebDNA 5.0 upgrade policies (2003)
WebCat2.0 [format thousands .0f] no go (1997)
includes and cart numbers (1997)
setLineitem blues (2000)
[input] .... [/input] usage (2005)
vs (1997)
WebDNA Solutions ... (1997)
"top" Clarification ( for apache ) (2008)
WebCat2b15MacPlugin - showing [math] (1997)
Sharing DBs across domains (2001)
search results not sorted with 'cl' (1998)
F*** you (1998)
founditem align (1998)
randomness (1997)