Avoid potential NullReferenceException

[haacked]

If someone sets BaseUrl to null, it shouldn't throw a NullReferenceException. Either it's an InvalidOperationException or it should just set the value to null and not complain.

I took the latter approach.

[ayoung]

Just curious, but what would you expect a request to hit when a baseUrl is null? Haven't tested it myself but I think the underlying HttpWebRequest would throw a NotSupportedException if it doesn't find a supported URI scheme.

[haacked]

@ayoung: I'd probably expect that someone else is going to set it later. It's not any different than calling the default empty RestClient constructor. That doesn't set the BaseUrl to anything so I assume it remains null and the exception is thrown later when you try to do something.

If you don't want the object to ever be in an invalid state, you'd have to remove the empty ctor and perhaps throw an InvalidOperationException on the BaseUrl setter.

[ayoung]

@haacked meh!

thanks.

[haacked]

:)