URL as an argument

In order to reuse a view for multiple urls or files, the 'advanced query settings' needs to be expanded to support more advanced features. An example of this might be, if you were requesting from a location with a sequence, like http://example.com/calendar/$month/$day/$year, then it would be great to be able to set those without having to clone a view 365 times. Or if you have a local directory of files that have the same schema, like product/1.export and product/2.export etc, then you'd be able to reuse the same view for all of them

One approach is to allow arguments in the query settings that read from the argument (contextual filters?) setting to fill the request location.

Another approach, though probably too complex, would be to add a data parameter to rb_views to support the url. Rules would probably be a good mechanism to handle numeric sequences (and others), but this wouldn't conflict with an arg feature, so it doesn't really make sense to attack directly from this angle.