Windows: Timer APIs are not Security APIs
authorDan Mihai <Daniel.Mihai@microsoft.com>
Wed, 19 Apr 2017 22:41:11 +0000 (15:41 -0700)
committerDan Mihai <Daniel.Mihai@microsoft.com>
Thu, 27 Apr 2017 03:33:36 +0000 (03:33 +0000)
There are currently no callers inside IoTivity that are dependent on
these registerTimer and unregisterTimer exports. Also, callers can
get access to these APIs by linking with static lib c_common.

Given these circumstances, one might argue that octbstack.dll should
not exports these two functions. But, they were already exported in
IoTivity 1.2, so they might be important for compatibity with
hypothetical already-existing IoTivity apps on Windows.

Change-Id: I708d8230e3b6e2f631e89fae2d9b3fab41c93108
Signed-off-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/19239
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Kevin Kane <kkane@microsoft.com>
Reviewed-by: Dave Thaler <dthaler@microsoft.com>
resource/csdk/stack/octbstack_product.def
resource/csdk/stack/octbstack_product_secured.def

index ba2216f..e43ff97 100644 (file)
@@ -148,3 +148,6 @@ oc_log_set_module
 oc_log_write
 oc_make_console_logger
 oc_make_ostream_logger
+
+registerTimer
+unregisterTimer
index bed33ff..14df087 100644 (file)
@@ -75,6 +75,3 @@ SetUserConfirmCB
 UnsetUserConfirmCB
 SetVerifyOption
 VerifyOwnershipTransfer
-
-registerTimer
-unregisterTimer
\ No newline at end of file