-
-
Woot! I've just received an SMS from Google Calendar reminding me of an event due in an hour. The greatest part? I'm in Israel. Who would have thought Google would support this feature for a market as small as Israel?
Here's a list of carriers supported by Google Calendar: "Which mobile providers does Google Calendar support?".
Currently 2 of Israel's cellular carriers are supported: Orange and Cellcom. Who's missing from the list? Pelephone of course. That company always ends up last in the race to adopt new technologies. I really should cancel my old subscription with them.
How to setup event notifications by SMS on Google Calendar then? Here's the step by step:
- Log into Google Calendar. Click 'Settings' then click 'Notifications'.
- The bottom section of the page is titled 'Notify me on my cell phone:'. There you choose your country and enter your phone number (no need for the international prefix).
- Now click the 'Send Verification Code' button. An SMS will be sent to the phone number you've entered, containing a verification code.
- Enter the verification code and click the 'Finish Setup' button. You're almost done.
- Now you can return to the top of the page where it says 'Choose how you would like to be notified:' and check the SMS checkbox next to where it says 'Event Reminders'
Enjoy!
-
-
This is a bit on the "old news" side of things, but have you heard of SeaMonkey? SeaMonkey is FireFox's smaller, uglier but faster brother.
SeaMonkey is a web browser from the Mozilla Foundation that's based on Gecko - the same "layout engine" as FireFox. That means it renders HTML to your screen the exact same way as FireFox does.
The difference? While FireFox uses the fancy, but "expensive", XUL for its user interface, SeaMonkey uses the native UI elements of whatever OS it runs on. SeaMonkey has less features and looks uglier but runs faster that FireFox and consumes considerably less system resources. SeaMonkey now has versions for Windows, Linux and OS X.
Because it relies only on native UI elements, it looks considerably worse than FireFox but runs considerably faster. It also has a lot of FireFox's functionality like a password manager, a javascript console and more.
SeaMonkey is no FireFox. I wouldn't use it as my default browser here at work on my powerful desktop station. But on occasions where you have limited CPU or memory resources, it's very useful. Its quicker response times are highly appreciated on slower machines.
Followup to original post: Thanks to all commenters. I stand corrected: SeaMonkey also uses XUL. Its faster-than-FireFox performance can be attributed to having less features written in leaner code.
-
-
I've stumbled upon behavior that I cannot understand in ASP.net's handling of the Response.Cookies object.
The trigger for this post is a page where I have Response.Flush() followed a bit later with an attempt to write an HttpCookie to the Response. Everything works fine when I try to write the cookie like so:
HttpContext.Current.Response.Cookies[name].Value = value;
But when I use this alternate method:
HttpCookie httpCookie = new HttpCookie(name, value);
HttpContext.Current.Response.Cookies.Set(httpCookie);
I get this exception thrown at me:
"Server cannot modify cookies after HTTP headers have been sent."
The unsettling part is that the second situation makes more sense to me than the first. Why? Because once Response.Flush() is called the HTTP headers have indeed been sent to the client and setting a cookie's value (which is done through HTTP Headers) should not be possible.
Why then is it okay to do this (set a cookie after HTTP Headers have been flushed to the client) if I'm using the indexer [] instead of the Set() method?
Your insight will be greatly appreciated :)