Lists all of the journal entries for the day.
Mon, 25 Aug 2003
10:23 PM - jj
I finally added the template system. It certainly took long enough.. only 3 hours of work too. I'm half way through the overrides as well. I have a few other suprises planned for this site soon.
12:18 AM - Give us a week will take off the weight...
That was a terrible jingle, but it fits my mindset about going back to college.
12:09 AM - Just Journal and MySql
I just tweaked some of the tables on jj by converting them to Inno DB. It was much easier than I thought. I will check the memory setting later and verify they are set properly.
So far so good. I did do a backup of that table before doing it. I will change the articles table on foolishgames.com as well if i like the benefits.
I'm planning on writing a script to do backups soon. I want to automate the process. (better yet bring the database down once a month and do a binary backup) Of course, i would have down time with jj if i did that. I will probably end up doing that every three months and doing regular mysqldump procedures otherwise. (on a side note, mysqldump is not working right since i ugraded to 4.1.0 alpha)
My webserver project hit a snag.. its called threading hell. My first version had flawless threading, then i switched to someone else's code base and his sucked. Now I am trying to refactor the code to use a new system i devised. I'm getting permission errors like crazy on the threads. I think i figured it out though.
Here's my thoughts:
my pooling system needs to start 10 threads (probably less in future.. maybe 6 like apache?) using a class that extends thread. Next i need to make an object pool of tasks i want run on the thread that implements runnable? The threads get notified using notify or notify all, one wakes up to clean the pool?
I'd rather hand off the socket to another thread and process that but i don't see how that woudl be done. If i get this figured out, i want to create a seperate logging manager with several threads to handle logging, plus run some type of status system, signal system on seperate threads. (this thing will almost need a second processor at this rate huh? )
I love the idea of getting status information on all the active threads like apache 2's controller does with lynx.
All well.. maybe i'll get this figured out someday.