The BrowseName is tracked in binary trees in other nodes for fast
lookup. We would have to reinsert the node to all references lists
of other nodes pointing here.
* previousSecurityToken structure of UA_SecureChannel was not cleared
after generating the new remote symmetric key. This caused a server
to renew the remote key every time a message chunk was received. If
the client requested a renewal of the secure channel and new nonces
were exchanged, but the client continued to use the "old"
SecurityToken for some more message chunks the server generated a
remote key based on the new nonces when it should have used the key
of the current SecurityToken.
* UA_SecureChannelManager_cleanupTimedOut() changed currently used
SecurityToken to the next one if present. According to Part 4,
chapter 5.5.2 OpenSecureChannel the server shall use the existing
SecurityToken until it expires or the server receives a message
secured with the new SecurityToken. Hence, it shouldn't trigg itself
change the SecurityToken.
* Fixed issues in renew channel test cases of the client
The server config is simplified a bit. A single timeout is used for the
request. No changes to the public API otherwise.
Full integration tests for the async operations.
* Implemented async subscriptions/monitored items
* Extended custom callback to hold UA_Client callback specific data
* Distinguish between user and UA_Client specific callback data
* Memory management for client-specific callback data (deleter)
* Updated current highlevel_async functions to new interface
* Fix: memory issues in async subscriptions/monitored items
clang analyzer memory issues addressed
* Fix codacy errors in async subscription/monitoreditems
* Memory fix: MonitoredItems_CreateData_free(..)
* Memory fix: UA_Client_MonitoredItems_delete_async
Async handler did not copy the request into CustomCallback::clientData
* Fix: portability issues with cppcheck+gcc4.8
* Fix: callback handler for delete_subscription_async was not called
* Added test cases for async subscription functions
* Fix -Werror=c++-compat in async subscription/monitoreditems tests
* Satisfy clang-format for async subscription/monitoreditems implementation
* Rebased to master and applied clang-format again
* remove CustomCallback_new(void)
* Change UA_malloc to UA_calloc when needed
* Remove CustomCallbackDataDeleter and use stack allocation for subscriptions.
Requires the use of a flag to distinguish stack allocated data from
heap allocated data in the subscription/monitored items implementation
* Fix C++-compat warning
* Fix: clang-format for changes
* Fix: uninitialized variable on conditional jump
* Remove all UA_EXPORT occurrences from ua_client_subscriptions
* clang-analyze: fix argument to free() is the address of local variable
clang analyzer cannot infer from
memset(&cc, 0, sizeof(CustomCallback)) that CustomCallback.isAsync is false.
Iadded a __clang_analyzer__ only statement that explicitly sets isAsync to false
using preprocessor macros.
* Bugfix: async monitored items memory leak
* Satisfy clang-analyzer for creation of monitored items
This commit drops the 'ua_' prefix and changes the public includes
to the form `#include <open62541/server.h>` instead of the old
`#include <ua_server.h>`
The following commits where squashed in this commit:
* client_historical_data: Bugfix isInverse
* client_historical: Cleanup and refactoring to meet pr comments.
* client_historialdata: Add a test for client historical read raw.
* historical_client: support index range
* historical_client: refactoring and cleanup methods.
* historical: Make the build system configurable and rename server test.
* historical_data: cleanup
* client_historical: Add code for events and modified history
* client_historical: fix memoryleak
* hda_client: Fix client_historical example.
This commit adds asynchronous services to open62541 on client side
* Asynchronous service (highlevel read/write) are available through the API that is defined in
ua_client_highlevel_async.h
* Besides the services, the connection procedure is asynchronous as well.
* A client Application that uses the asynchronous API
adds requests by calling an asynchronous service (e.g., UA_Client_sendAsyncReadRequest(), UA_Client_sendAsyncBrowseRequest() )
checks for response with UA_Client_run_iterate() repeatedly
and processes the responses with user-defined callbacks
Julius Pfrommer