Subject | Re: Proof Sandman keeps running from. |
From | Sandman |
Date | 07/31/2009 20:45 (07/31/2009 20:45) |
Message-ID | <mr-CDB3EE.20455731072009@News.Individual.NET> |
Client | |
Newsgroups | comp.os.linux.advocacy,comp.sys.mac.advocacy |
Follows | Steve Carroll |
Followups | Snit (42m) > Sandman Tim Adams (2h & 38m) |
Indeed you did. What you didn't do was say something like, I don't know:Steve CarrollSteve CarrollSandman
Anyone wanna take a stab at what caused this;)
Fixed. My bad, actually :)
Thanks for pointing out an error on my page in a reasonable mannner that I could swiftly fix.
I did what any reasonable person would do (hehe;)
Of course not. Any given page in Atlas takes CSS instructions from at least 10 different sources, depending on what application you're using. Not only that, with some applications, like the blog application, the users can define their own styles (through a web interface) to style their blog to some extent.SandmanSteve Carroll
Actually, the "system" (CMS) I'm using is called Atlas and is developed solely by me.
After having worked (interspersing my own php code, html, css, javascript) with things like Drupal, Wordpress, Joomla, etc. I can certainly see how errors can be tossed out. I can even see how difficult it would be to track them down depending on the error. This is *nothing* like creating a website from a Dreamweaver template or even making your own site from scratch using DW.
It's hilarious to watch gluehead try to compare these two very different things... I'd like to see that idiot code up a CMS from scratch. He's even aware that you coded the CMS from scratchIndeed, during our "truce" which was quick to break he was given the option to ask questions which I answered (at least most) and those answers are totally forgotten by him now. I answered his questions as I would answer any question you would ask me.
yet, he's still trying to compare his errors to those generated by tons of code that generates markup, code he likely couldn't even recognize. Of course, he is an "IT teacher" so maybe he writes these kind of systems from the ground up all the time and never has any errors (yeah, right;)
)
It's really not. From the beginning it was a live fetch, meaning that the DB was accessed for each and every page request (hundreds of thousands per month) which was a performance nightmare. It's being cached now, but when the data comes from a DB, it's a lot harder to determine when to recreate the cache, and I am currently aggregating it at certain points (every five minutes) which means that there is a lag between editing the DB and seeing the result. With flat text files, you can always compare the file dates between the original and the cache and determine when to recreate.SandmanSteve Carroll
That means that the CSS (for example) isn't contained as plain text in a text file, it's actually compiled from a number of sources, even database and sent to the browser, at which point errors could be made when parsing or rendering the data.
Ah... I've never done this as coming from a database... sounds interesting.