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)
commitb5b86ce52c0251101bb2db4593d7c352c3c92001
tree4f8fbc876ed093e1745e1abf09970f59f0a75649
parent4aa1474b84b7f16353da64808d03634affa99a77
Windows: Timer APIs are not Security APIs

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