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:
Search question (1999)
URL encoding (1998)
[OT] (waaaay OT) further off topic than before (2004)
Nested tags count question (1997)
Re:2nd WebCatalog2 Feature Request (1996)
Converting Quotes in Javascript (2001)
Calculate UnitShipCost in Formulas.db (1999)
ShipTotal Yet Again (1998)
encryption madness (2003)
[WebDNA] Triggers not working (2011)
ssl and invoic.tpl and back bttn (2002)
Rendering out a page (1997)
Location of Webcat site in folder hierarchy (1997)
Emailer help....! (1997)
textarea inputs and returns (1999)
PIXO (1997)
RE: Answer: WebDelivery downloads alias, not original ? (1997)
[WebDNA] Trigger troubles (2014)
Keep away (1997)
Search design (1997)