because a Reverend can't be wrong.
Apparently the upgrade to MT 2.61 isn’t the only thing that is causing my “Out of Memory” errors. Because I’m still getting them every now and then when using 2.51. This leads me to believe that the reason behind this is my recent import of over 1500 entries from LiveJournal. This means the MovableType is probably loading some portion of that data into memory and leaving it there while it attempts to rebuild a page. That isn’t really a good idea.
Suggestions? Solutions? Crack cocaine?
I’ve run into another stumbling block in my coding of inklog, and I’m not exactly sure how to proceed. I know HOW to code the problem fifty different ways, I just don’t know which way is best. And it is a very important design choice, as the rest of the application will use the same principles. “Let me explain; no, there is too much; let me sum up.”
On each “page”, one has the ability to place multiple components. I’m not sure if each component should have its own template and be parsed separately (making the system easier to use, but less flexible), or if all the datashould be collected and shipped to one template per page. Additionally, I’m not sure if I should place the component reqestors inside the template locking the user into the template system of my choice and providing each piece of a template to be capable of existing on its own (easier to use), or if the components should be requested by the calling page making each piece of the template have knowledge of the request that is parsing it but, therefore, not tie the user to my template system (more flexible).
So I guess, what it boils down to is this: should I make it easier to use, or more flexible?
This morning I upgraded MovableType to the NEW version 2.61, then it broke. Some how, while my server is very capable of running MovableType 2.51 and has done so without error for some time, version 2.61 causes my Perl interpreter to issue “Out of memory” errors. Yay!
So, I’ve downgraded back to 2.51. The new features weren’t that great anyway. Really, the only reason I was upgrading was to check out the undocumented feature [via phil ringnalda], but it turns out it isn’t much anyway. I also patched MovableType to fix its new found vulnerability.
The good thing is that this has prompted me to begin coding inklog again. (By the way: I really dislike that, as of today, Phil‘s mention of inklog earns a higher google result number than my own. Hopefully, this entry will fix that.)