|
I think the answer is "no"... here's the situation: An application based on SQL Anywhere web services currently uses unfriendly names for the web services... CREATE SERVICE unfriendly ... AS CALL whatever ( ... ); CREATE PROCEDURE whatever ( ... ) ... and the wish is to present more friendly service names to the web browser, implementing the change over time without immediately disabling the old names, so duplicate service definitions are proposed... CREATE SERVICE unfriendly ... AS CALL whatever ( ... ); CREATE SERVICE friendly ... AS CALL whatever ( ... ); CREATE PROCEDURE whatever ( ... ) ... Considering that the rate of service invocations will not change, and that each invocation will use either the old name or the new name, will there be a performance penalty other than the miniscule overhead for more stuff in the system catalog? |
|
Breck: you are correct. There will be a small but negligible performance penalty to have the additional entry in the syswebservice table (and hence another entry to find or skip over when matching the URL to the web service), but beyond that there will be no effect. Calling the same procedure from different web services is not a factor what-so-ever. Note: Within the procedure you can use http_variable('@HttpURI') to get the URL that was used to access the web service (in case you want to determine if anyone is using the old 'unfriendly' service). |