Last year in September, my parents and I embarked on Raible Road Trip #6 when returning from Web Design World 2002 in Vegas. Julie didn't join us since she was 7 months pregnant. However, Raible Road Trip #7 will be Julie, Abbie and I - and it begins this weekend. I'm starting to get really excited about it. We bought our plane tickets last night, and tonight we started planning the trip. Here it is so far - thanks to all for your suggestions.
- Fly into San Diego on Saturday morning. Stay with Julie's sister until Sunday afternoon or Monday morning.
- Drive like a bat out of hell to Big Sur, which is about 8 hours according to MapQuest. Stay a night or two - those cabins that Andy mentioned sound nice.
- From Big Sur, head to Bodega Bay. I'm a backwoods Montanan, so I don't know about San Fran - we might just skip it. It sure sounds cool, but I also know it's pretty crowded. I happened to remember one of my best friends (that I haven't talked to in years) actually lives in Bodega Bay - so I called him up tonight. He's fighting fires in Montana, so he might not be there - but his wife, Katie, and son will be there - so we'll probably stay with them for a night or two. This brings us to Thursday or Friday.
- Our end destination is meeting my parents at the Oregon Caves on Friday or Saturday, so we'll probably head from Bodega up there (7 hours). Hopefully, we'll catch some redwoods along the way.
- My dad has a couple rooms booked at Crater Lake on Sunday and Monday night. My sister, Kalin, is meeting us on Saturday.
Boy this is gonna be a fun trip. I haven't been on a road trip on California since I was a little kid. It was in the early 80s and my dad had a rigged up canvas topper on VW Rabbit pickup. We camped every night and drove like maniacs during the day. Abbie will be too young to remember, but that's what the ol' camera is for!
If you have a secure server setup like I do, I think you'll find that WinSCP (Windows) will make your life much easier.
I've recently been tasked with rebuilding a JSP-based site using a Struts architecture. One of the issues (that I see) in the current architecture is that there are a number of JSPs with the text for the pages hard-coded in them. After re-writing this app, we plan on deploying it to 25+ customers - and we certainly don't want to have 25 different JSPs (with text) for each customer. I've proposed a database, but that might be a little resource intensive - so I'm wondering how folks have done this in the past (I'm sure it's been done before)?
Options I see are:
- A Database table with the following columns (page_id, title, content, section_id).
- Text files that are imported using <c:import url=""/>
What options have you used (feel free to add more) - if you've used the database approach - how do you define the page table? Maybe we should use the Roller way and use Velocity and OSCache.
I formatted the Red Hat hard drive on the machine they gave me at work today - installed XP and went to a meeting. We got interrupted in the meeting for lunch, and resumed the meeting after lunch. After our meeting finished, I was pleasantly surprised to see XP had finished installing (I stopped by every-so-often to kick it into gear again). Later this afternoon - about 10 minutes ago - the Network Admin came by to yell at me for getting blasted. I didn't even do anything but install XP and this damn little virus got me. And I was so proud for not getting it at home. Lesson learned? Every time you install XP, unplug it from the network and install a firewall before going further.
