Aching Ilia

(thank goodness for crossword puzzles, othewise I would never know ilia=hipbone)

Ouch, I feel like I’ve been shot in the hip.  But this is unlikely because A) I think I would have noticed someone shooting me in the hip and B) I would have some external signs of having been shot in the hip and C) if A and B are the only reasons I can come up with to dispel the possibility of having been shot in the hip then that is pretty pathetic.

I must have slept wrong, or sat wrong, or looked at my hip wrong because I have what feels vaguely like a muscle strain or a pinched nerve and it’s driving me up the wall.  I’ll be sitting here doing my work and I reach over to grab my bag of gummy bears and a shooting pain goes through my hip.  Shooting pain, getting shot in the hip, see, there’s a connection.

I’ll just have to stop acting like a baby every time I feel the fire in my loins.  Don’t loins include hips?

I just got an electronic newsletter from my insurance company.  The lead story and subject of the email is "Six Flammable Foods."  Now THAT is an eyecatching lead.  Of COURSE I opened the email and the newsletter because I want to know what the TSA will next be prohibiting in airports and on planes.

Here’s the list of six flammable foods:
1. Garlic.  Who knew?
2. Bacon.  Ok, I knew that bacon grease was dangerous, especially if you fry bacon in the buff, but flammable?  I didn’t know that.
3. Deep-fried stuffed peppers.  I think there might be food that you WANT to burst into flames, and deep-fried stuffed peppers is one of those.  Can you stuff the peppers with fried Three Musketeers bars?
4. Flour.  Graneries blow up all the time from the fine dust, this one doesn’t surprise me.
5. Alcohol-based sauces.  Shouldn’t this one include alcohol filled bottles with rags stuffed into the opening?
6. Peanut brittle and other ultra-sugary foods.  The warning refers to combustion during the making of these, not to the peanut brittle that you have wrapped in a napkin in your jacket pocket.  Darn.

Another article in the same e-newsletter is titled "Why do funerals cost so much?".  Isn’t it obvious?  The funeral home has to clean up after all the flammable food.

I had to bear the pain and reach for the gummy bears.  I couldn’t take the chance that they would burst into flame.  I’m not as concerned about burning down the office as I am of losing a gummy treat.

I have a personal website that I use as cloud storage and for sharing some old high school photos.  I have an applicaton that I recently copyrighted and I’d like to tie the application to the website so I can do "license" checks when someone uses my application.

I think I want a small database with a username and hashed password and a webpage front end.  I see the application pushing the username and hashed password to the webpage and having the webpage check both against the database and return a go/no-go that the application uses to permit/deny continued usage.

What do I need to make the webpage/database talk to each other on a server?  I don’t need a full blown solution, but I would appreciate some hints on how to do this.  Does anyone know?  Don’t make me get out my garlic and flour. 

No baseball games to go to this week, the Nat’s are out of town.  That might give me a chance to cut up my piece of cherry wood and make a soap mold.  Depending on how nice it comes out, maybe I’ll sell it and start making more.  After all, I’ve already got the website.

Ender is out.