You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently $mthd is used to decide both the Method and whether reading or writing is occurring. This should probably be separated. Then, it might be better if a variable could be set to override this behavior (or config option).
The reason I bring this up, is my hosting services restricts the query string value lengths by default to 512, and my SPARQL queries were running ~800 in length. I'm fixing my account, but it got me thinking... maybe it would be better to have a config option for using GET or POST.
Also, the current implementation uses the "$mthd" (method) to decide whether to use 'store_read_key" or "store_write_key". Instead, a variable called "$is_read_operation" could be used.
The text was updated successfully, but these errors were encountered:
Currently $mthd is used to decide both the Method and whether reading or writing is occurring. This should probably be separated. Then, it might be better if a variable could be set to override this behavior (or config option).
The reason I bring this up, is my hosting services restricts the query string value lengths by default to 512, and my SPARQL queries were running ~800 in length. I'm fixing my account, but it got me thinking... maybe it would be better to have a config option for using GET or POST.
Also, the current implementation uses the "$mthd" (method) to decide whether to use 'store_read_key" or "store_write_key". Instead, a variable called "$is_read_operation" could be used.
The text was updated successfully, but these errors were encountered: