Posts on this site are never sponsored.
The city of New Westminster hadn’t seen a first-run movie theatre since 1985 when Columbia Cinemas closed its doors. As part of the Plaza 88 complex (now called Shops at New West) built around the New Westminster SkyTrain station, Landmark Cinemas opened in May 2012.
The theatre is clean, well-kept, and has comfortable seating. (Although, as of the time this was written, the theatre is only 2.5 years old.) You can buy tickets online, at the concession, or at a row of machines at the entrance. You get to choose specific seats at no extra cost. This is nice as you don’t have to go extra early and hang around to claim your seat.
Landmark Cinemas in New Westminster has 10 screens. It is a quieter, convenient alternative to SilverCity Metropolis at Metrotown (in Burnaby).
Regular general admission is $11.25, and matinees are $9. 3D movies are more expensive. On Saturdays and Sundays, there are morning movie showtimes for only $6.25, which is a cheap way to enjoy a little weekend luxury!
Varnish Cache is a high performance reverse proxy with an easy-to-use configuration language. However, there are lots of things that you cannot do by default in a Varnish configuration file. For example, you cannot reliably read response cookies because Varnish only reads the first “Set-Cookie” header.
Therefore, you sometimes need to use Varnish extensions, called “modules” or “VMODs” to provide additional functionality. One of the most popular modules is the “header” module, which enables you to reliably read response cookies, among other things. You have to compile Varnish modules and place them in the “vmods” folder, which is typically /usr/libs64/varnish/vmods. Before Varnish 4, you had to compile them against the source code of Varnish itself. Starting from Varnish 4, you can compile them against the running Varnish installation. In other words, you should be able to just download the module code, then run the commands ./configure, make, and make install from the downloaded module code directory. You just have to install the “varnish-lib-devel” package using “yum” on CentOS / Red Hat (or “libvarnishapi-dev” using “apt-get” on Debian / Ubuntu).
Compiling code is a rather foreign concept for many developers and it would be nice to have the compiled Varnish module files for the major operating system versions available for download. That would make the installation process much easier! Here is the Varnish “header” module compiled against Varnish 4.0.2 on 64-bit CentOS 6.5.
I’m a fan of XE Trade for making online currency transfers, and most of all for sending money internationally.
If you go to xe.com, you’ll find the mid-rate exchange rates. The rates provided by XE Trade are always “worse” than the rates on xe.com, since XE Trade adds their own margin. I’ve discovered that XE Trade rates are always even worse on weekends; I decided to record the spread on various days for the USD to CAD exchange rate. Here’s a sampling of the exchange rate spread from September 2014 taken on different days at random times of the day.
||Day of week
|September 12, 7:32am Pacific
||Friday, 4:40pm Pacific
Bottom line: use XE Trade only on business days! Also, according to the sample from late on Friday September 12, you should make sure to do any currency trades before markets have closed. Based on my tests, the average spread on business days was 1.622%, whereas on non-business days it was 3.5985%. That’s almost a 2% difference.
On a related note, if you are making USD-CAD currency transfers within a business account in Canada, some of the banks’ currency exchange services might provide better rates than XE Trade. Specifically I’ve found that RBC‘s rates are often better than XE Trade. It’s much more of a pain trying to send money internationally from a business account using RBC, though!
I was using Notepad++ to edit a file in Windows 7 when the program suddenly emptied the file, saved the empty file, and crashed. Nevermind the fact that this was an alarming occurrence for a code editor, but I didn’t want to lose my work. I believe this was caused by its relatively new (in version 6.6.x) “session snapshot & periodic backup feature”, which I hope has since been patched. The problem has not happened since a couple of months ago, only happened once, and a few updates to 6.6.x have since been released. Although, since that occurrence I have been using Notepad++ less.
The good news about the periodic backup feature erasing all my work is that it was also the one that restored my work. I was able to find the folder C:\Users\<my_username>\AppData\Roaming\Notepad++\backup, in which there was a copy of the file just before Notepad++ had emptied it.
If you’re looking for a different code editor for Windows, check out the more fully-featured but not as lightweight Sublime Text or Netbeans.
Much of the documentation regarding Varnish logging is around varnishlog (makes sense, considering the name), which parses the Varnish request and response logs from system memory. However, what about when you’re building or troubleshooting your VCL configuration file and want to dump specific variables or messages to a file? This is not widely documented but quite easy to do.
The key function is std.syslog. In order to use that function, you simply have to enable the std (standard) Varnish module, which is the only built-in “vmod” and is thus natively available and doesn’t have to be compiled.
To enable the std module, simply put this at the top of your VCL file:
Then, you can use it in any of the VCL functions like this:
std.syslog( 180, "VARNISH: Invalid cookie found." );
Or, add in some variables to your log message:
std.syslog( 180, "VARNISH: beresp.ttl is " + beresp.ttl );
This will log the message to general system messages log, which is often at /var/log/messages on Linux operating systems. The first parameter, which is 180 in the examples above, is the priority value.