Geeks unite! What a couple of weeks we have coming up, and things are going to be awesome! Here are some events I will be attending and I hope to see you all there!

Ignite Salt Lake

March 4th will mark the 4th Ignite event in Salt Lake City, at the State Room (21+). The event opens at 6:00PM.

As is tradition with Ignite there will be a building activity to start things off, this time the construction materials include twisty ties and 5,000 little green army men, that sounds like fun

Following the build they are going to have two session of 9 talks each, each talk lasting only 5 minutes.

The pace is fast and the talks sound interesting this go round:

• James Young – You sunk my Battleship!
• Jason Vance – 15 things to remember when dating in a post Apocalyptic Zombie Environment
• Matthias Shapiro & Jason Alderman – Mobile App Dev RAP BATTLE (this should be awesome!)
• DJ Waldo – Dude
• Kellen McAffee – How to tell your friends that you’ve seen a sasquatch

The event is free, and really fun. I encourage all (over 21) to attend this event, you will not be sorry.

Hostlers Model Train Festival

March 5th through the 7th will be the dates for the Hostlers Festival where over 8000 people will come to see the finest in model train setups.

The Hostlers were formed in 1988 and by 2004 had over 180 members! They specialize in all scale modeling, and love to spread the joy of model trains to all.

The event is $5 at the Union Station in Ogden. Hours are posted at http://www.hostlers.info/

Last year they had some really impressive setups and some excellent vendors. This show is a great one for taking the little ones too, they will love all the working models.

Also take time to go through the Utah State Railroad Museum while you are there.

Today I was offered a free lesson in how PHP handles Soap, and more specifically WSDL caching.

When you instantiate a PHP Soap Class you pass it a WSDL (Web Services Description Language) and it looks like this:

$client = new SoapClient('http://example.com/services/thescript.php?wsdl');

Depending on how your caching is setup, this will go out to the WSDL provided, pull in the document and store it in a cache. The default cache for PHP is 86400 seconds. If you are familiar with time in seconds you know that that is 24 hours. So by default you only actually read the WSDL once in a 24 hour period. Normally this is not a problem.

What is a WSDL?

For that answer let’s turn to the W3 site:

WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.

So in English that means it is a map to the services provided by the provider. Basically you get a copy of the map, and follow the endpoints to the answers you need.

One basic function of this is that it tells you want methods (services) are available on your fresh client.

When WSDLs go bad

So today one of my providers, without warning, updated their WSDL. This wreaked havoc on my system because I had cached the WSDL on my side for 24 hours (remember, the PHP default). The change was a super simple change, a change in URL for a service, that’s it!

The problem was that since PHP had already read the file within 24 hours it didn’t care that there was a new file, that the URLs had changed, and so it continued to work as it had before.

The real problem wasn’t that the URLs changed, that would have been fine if the provider hadn’t shut off the previously reported URLs.

Turn off the cache

So you are left with two options when something like this happens. First, you can sit and wait up to 24 hours for the problem to fix itself. This was not an option for us. The second is to clear your cache and try again.

Now PHP (on Linux) stores the cache for the Soap WSDL in /tmp and I wasn’t sure which one of the many files was the actual cache for this particular provider so I decided I would have to tell PHP to not cache the WSDL and try again.

Into php.ini I went, located the soap.wsdl_cache_enabled flag. I changed it from 0 to 1

soap.wsdl_cache_enabled=0

I saved the file and restarted Apache.

The service continued to fail. I was perplexed. I thought maybe I flubbed the save so I opened the php.ini again located my line and it was fine. So I looked around there to see if maybe I missed another important flag. The only thing I could find was soap.wsdl_cache_ttl listed as the “(time to live) Sets the number of second while cached file will be used instead of original one” I promptly changed this to 0 as well

soap.wsdl_cache_ttl=0

Restarted Apache, and finally my script stopped failing.

I have since re-enabled my cache ttl and enabled flags, as reading the WSDL every time is a resource hog that doesn’t need to be in place.

The Lesson Learned

The lesson learned by all today is be aware of your caching, and be aware of the changes you make to your live/production systems.

I would like to give a big thanks to all the folks who attended today’s Salt Lake Linux User Group Daytime Special Interest Group (SLLUG Daytime SIG). We had a great time covering the basics of vi(m) and I think everyone walked away knowing something new.

I created my slides using Google Docs, so you can see them too!

I want to thank Joe Brockmeier, and Linux.com for the source material and here is a list of places you can find equally great (actually better) presentations and tutorials on vi(m):

• Linux.com — just click the link to search the site for vim
• Vim 101
• Vim 201
• Viemu Cheat Sheet (herlo pimped this during my presentation)

Also to learn more about vi(m) read up on these:

• Vim 301
• Vim 401

There are thousands of other articles on vi(m) around the net, so if this doesn’t give you your fix, search Google.