Thought I pose this as a question in case anyone out there had an insights/preferences.
Consider the following URL:
http://localhost/myapp.fcgi?test
Where test is the query string.
In the current VbFcgi implementation, test is treated as a default parameter value. Calling CHttpQueryParams.DefaultValue returns test, and calling CHttpQueryParams.ValuesByKey("") returns a CHttpQueryParamValues object with a single value of test.
I'm thinking it might be better to treat test as a "flag" and use it as a key instead of a value. So calling CHttpQueryParams.Exists("test") would return True and calling CHttpQueryParams.ValuesByKey("test") would return a CHttpQueryParamValues object with zero values.
Perhaps the best of both worlds would be an option property to let users decide which approach to take based on the needs of their FCGI applications?
Thought I pose this as a question in case anyone out there had an insights/preferences.
Consider the following URL:
http://localhost/myapp.fcgi?testWhere test is the query string.
In the current VbFcgi implementation, test is treated as a default parameter value. Calling
CHttpQueryParams.DefaultValuereturns test, and callingCHttpQueryParams.ValuesByKey("")returns aCHttpQueryParamValuesobject with a single value of test.I'm thinking it might be better to treat
testas a "flag" and use it as a key instead of a value. So callingCHttpQueryParams.Exists("test")would return True and callingCHttpQueryParams.ValuesByKey("test")would return aCHttpQueryParamValuesobject with zero values.Perhaps the best of both worlds would be an option property to let users decide which approach to take based on the needs of their FCGI applications?