What is WebDNA

WebDNA is a scripting and database system designed to easily build web applications.

WebDNA and BioType

BioType service is a biometric keystroke dynamic system. It will be part of WebDNA 8.5

Download WebDNA

Download WebDNA freeware, try it and register later if you want.

WebDNA resources

The list of all WebDNA instructions.
WebDNA
Software Corporation
Search WebDNA Site
 Menu


HOME


DOWNLOADS


LEARN


EDUCATION


NEWS


COMMUNITY


STORE


SUPPORT


CONTACT

Re: [BULK] Re: [WebDNA] abstraction code can be tricky...

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108315
interpreted = N
texte = Govinda wrote: >>> webdna's allotted ram-usage limit > > for lack of a better term, I called it that ("webdna's allotted ram-usage limit"). > > Let me explain: > > Obviously the company line is that the only limit is the amount of RAM on the server machine. > > But coding aggressively has for some/many of us revealed a phenomena - that a page which tries to use "more RAM than what we usually gobble up with our code", can, when hit with the browser, simply never load in the browser.. and even if we then comment out (or delete) the offending code (note: *properly-sytaxed*, but just RAM-hungry code), then upon reload in the browser, Webdna keeps serving up an old copy of the file.. a copy which no longer exists on disk. And all this while webdna caching is turned OFF in the admin interface. I KNOW others beside myself have seen this. And I am not talking about a page that tries to use all 6GB of RAM that is sitting idle/available... (or so one would reasonably think).. but just code that pushes the limit just a little too far. > > Sound too fuzzy? Sure; it is hard to quantify, and describe, since I can't see under the webdna engine hood to know exactly what is happening. > > I tried to make my last post useful but just saying, effectively, "Hey, in case your page never loads, and your webdna cache seems to be stuck (for that page), then see if you are defining and calling a function within another function." > > HTH Govinda, I suggest you post a more terse version of your problem. I've been coding WebDNA just about every day for 10 years and have never seen an illogical caching problem. It's likely there is a reason for the results you are seeing.. proxy server, sandbox vs. admin setting, or whatever. Donovan -- Donovan Brooke Euca Design Center www.euca.us Associated Messages, from the most recent to the oldest:

    
Govinda wrote: >>> webdna's allotted ram-usage limit > > for lack of a better term, I called it that ("webdna's allotted ram-usage limit"). > > Let me explain: > > Obviously the company line is that the only limit is the amount of RAM on the server machine. > > But coding aggressively has for some/many of us revealed a phenomena - that a page which tries to use "more RAM than what we usually gobble up with our code", can, when hit with the browser, simply never load in the browser.. and even if we then comment out (or delete) the offending code (note: *properly-sytaxed*, but just RAM-hungry code), then upon reload in the browser, Webdna keeps serving up an old copy of the file.. a copy which no longer exists on disk. And all this while webdna caching is turned OFF in the admin interface. I KNOW others beside myself have seen this. And I am not talking about a page that tries to use all 6GB of RAM that is sitting idle/available... (or so one would reasonably think).. but just code that pushes the limit just a little too far. > > Sound too fuzzy? Sure; it is hard to quantify, and describe, since I can't see under the webdna engine hood to know exactly what is happening. > > I tried to make my last post useful but just saying, effectively, "Hey, in case your page never loads, and your webdna cache seems to be stuck (for that page), then see if you are defining and calling a function within another function." > > HTH Govinda, I suggest you post a more terse version of your problem. I've been coding WebDNA just about every day for 10 years and have never seen an illogical caching problem. It's likely there is a reason for the results you are seeing.. proxy server, sandbox vs. admin setting, or whatever. Donovan -- Donovan Brooke Euca Design Center www.euca.us Donovan Brooke

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:

date formatting for CC card expiration date check (1998) We have Proof (1997) WebSTAR plugin update (2004) WebDNA programmers needed (1998) Bug Report, maybe (1997) ShowNext Page Style (2003) Is there a max number of fields? (1998) PSC recommends what date format yr 2000??? (1997) I'm tired of all this! (2000) Error Log.db --however (1997) [WebDNA] Encrypt Method SHA256 (2018) [OT] Authorize.net (2003) Anyone here care to chime in? (2005) Re:FYI: Error message (1996) Help! WebCat2 bug (1997) service stop and restart (1997) RE: Renaming textA (1998) WebCatalog for guestbook ? (1997) problems with WebCat-Plugin () Public beta 2 for WebCatalog 4.0 is now available. (2000)