Re: [BULK] Re: [WebDNA] abstraction code can be tricky...
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108313
interpreted = N
texte = >> 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=
Associated Messages, from the most recent to the oldest:
>> 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=
Govinda
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:
X etc.... (1999)
WebCat2 - [format thousands] (1997)
[SHOWIF] (1997)
Signal Raised (1997)
Protecting Realms (1998)
Simple way to create unique SKU (1997)
Reversed words (1997)
Not really WebCat (1997)
can WC render sites out? (1997)
Use of Back and Reload Buttons on ShoppingCart page? (1997)
Help! WebCat2 bug (1997)
AppleScript/.db (was:FTP to WebStar) (2001)
Rhapsody? (1997)
WebCatalog for Postcards ? (1997)
MOOOOOO (2000)
NT Version on IIS 4.0 (1997)
French characters in variables (2001)
Re:Emailer and encryption (1997)
WebCatalog Technical Reference (1997)
We have Proof (1997)