[WebDNA] Still Having Problems - more

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 100215
interpreted = N
texte = --Apple-Mail-32-576665094 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Regarding the quote below and the "Phone Home" issue -- granted if it is checking in with the licensing server every 2 hours -- maybe it doesn't have any adverse effect immediately if the server is unreachable -- but what happens if it is unreachable for say 72 hours????? Was the "Phone Home" code ever designed in anyway to "disable" WebDNA -- that would lead to a "Sorry, WebDNA server not running" error message????? Yes or No??? No one has ever answered that... We talked about this to SMSI, particularely concerning the "phone home" suspicion; Scott told us "It has been awhile, and I do not have the code in front of me at the moment. But I do remember taking into consideration the possibility of the license server 'not being there' when the phone-home code is executed. So if the licensing log server is down, it should not have a negative impact on WebDNA engine performance. From memory, I think it was set to phone home every two hours." We will of course check into this deeply, but i doubt we will find anything that could explain the crashes in WebDNA code. - chris --Apple-Mail-32-576665094 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
Regarding the = quote below and the "Phone Home" issue -- granted if it is checking in = with the licensing server every 2 hours -- maybe it doesn't have any = adverse effect immediately if the server is unreachable -- but what = happens=A0if it is unreachable for say 72 hours?????

=A0

Was=A0the "Phone Home" code ever designed in anyway to = "disable" WebDNA -- that would lead to a "Sorry, WebDNA server=A0not = running" error message????? Yes or No???

=A0

No one has ever = answered that...
We talked about = this to SMSI, particularely concerning the "phone
home" suspicion; Scott told us

"It has been = awhile, and I do not have the code in front of me at = the
moment. But I do remember taking into = consideration the possibility of
the license = server 'not being there' when the phone-home code is
executed. So if the licensing log server is down, it = should not have a
negative impact = on WebDNA engine performance. =46rom memory, I think it
was set to phone home every two hours."

We will of course = check into this deeply, but i doubt we will find
anything that could explain the crashes in WebDNA = code.

- = chris
= --Apple-Mail-32-576665094-- Associated Messages, from the most recent to the oldest:

    
  1. [WebDNA] Still Having Problems - more (Bob Atchison 2008)
--Apple-Mail-32-576665094 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Regarding the quote below and the "Phone Home" issue -- granted if it is checking in with the licensing server every 2 hours -- maybe it doesn't have any adverse effect immediately if the server is unreachable -- but what happens if it is unreachable for say 72 hours????? Was the "Phone Home" code ever designed in anyway to "disable" WebDNA -- that would lead to a "Sorry, WebDNA server not running" error message????? Yes or No??? No one has ever answered that... We talked about this to SMSI, particularely concerning the "phone home" suspicion; Scott told us "It has been awhile, and I do not have the code in front of me at the moment. But I do remember taking into consideration the possibility of the license server 'not being there' when the phone-home code is executed. So if the licensing log server is down, it should not have a negative impact on WebDNA engine performance. From memory, I think it was set to phone home every two hours." We will of course check into this deeply, but i doubt we will find anything that could explain the crashes in WebDNA code. - chris --Apple-Mail-32-576665094 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
Regarding the = quote below and the "Phone Home" issue -- granted if it is checking in = with the licensing server every 2 hours -- maybe it doesn't have any = adverse effect immediately if the server is unreachable -- but what = happens=A0if it is unreachable for say 72 hours?????

=A0

Was=A0the "Phone Home" code ever designed in anyway to = "disable" WebDNA -- that would lead to a "Sorry, WebDNA server=A0not = running" error message????? Yes or No???

=A0

No one has ever = answered that...
We talked about = this to SMSI, particularely concerning the "phone
home" suspicion; Scott told us

"It has been = awhile, and I do not have the code in front of me at = the
moment. But I do remember taking into = consideration the possibility of
the license = server 'not being there' when the phone-home code is
executed. So if the licensing log server is down, it = should not have a
negative impact = on WebDNA engine performance. =46rom memory, I think it
was set to phone home every two hours."

We will of course = check into this deeply, but i doubt we will find
anything that could explain the crashes in WebDNA = code.

- = chris
= --Apple-Mail-32-576665094-- Bob Atchison

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:

WebSTAR virtual roots with . in the foldername (2000) Sendmail (1997) Emailer error 550? (1999) RE: [WebDNA] Latest Windows Version (2010) [if] (2003) [WebDNA] WebDNA 7 (2011) webcat2b12 CGI -- Date comparisons (1997) PCS Frames (1997) timezone calculations (2001) wrong input values? (1997) Nested vs conditional (1997) Page Counters? (1997) Images do not upload completely ... (2003) using showpage and showcart commands (1996) Re:WebCat Emailer & Liststar (1997) off topic (1999) Where's Cart Created ? (1997) RE: CloseDatabase (1997) Nesting format tags (1997) NT b19 sends extra MIME headers (1997)