CHANGELOG 4.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102
  1. This changelog reports changes to the public API. Internal refactorings and bug
  2. fixes are not reported here.
  3. 2017-08-16 jpfr <julius.pfrommer at web.de>
  4. * Default Attribute Values for Node Attributes
  5. The AddNodes service takes a structure with the attributes of the new node as
  6. input. We began checking the consistency of the attributes more closely. You
  7. can now use constant global definitions with default values as a starting
  8. point. For example UA_VariableAttributes_default for adding a variable node.
  9. * All nodes have a context pointer
  10. All nodes now carry a context pointer. The context pointer is initially set
  11. to a user-defined memory location. The context pointer is passed to all
  12. user-visible callbacks involving the node.
  13. * Global and node-type constructor/destructor
  14. The constructors are fine-grained mechanisms to control the instantiation and
  15. deletion of nodes. Constructors receive the node context pointer and can also
  16. replace it.
  17. 2017-08-13 Infinity95 <mark.giraud at student.kit.edu>
  18. * New/Delete methods for the server configuration
  19. The default server configuration is no longer a constant global variable.
  20. Instead, it is now handled with a pair of new/delete methods. This enables
  21. the use of malloced members of the server configuration. With this change,
  22. the endpoint descriptions are no longer generated in the server but are
  23. created as part of the server configuration. See the example server
  24. implementations on how to use the configuration generation. The change is a
  25. precursor to the encryption implementation that ties into the generation of
  26. endpoint descriptions in the server config.
  27. The generation of the default server configuration is implemented as a
  28. "plugin". So it comes with CC0 licensing and can be freely adjusted by users.
  29. The TCP port in the default configuration is 4840. This is the recommended
  30. port for OPC UA and now used throughout all examples.
  31. 2017-07-04 jpfr <julius.pfrommer at web.de>
  32. * Return partially overlapping ranges
  33. Test the integrity of the range and compute the max index used for every
  34. dimension. The standard says in Part 4, Section 7.22:
  35. When reading a value, the indexes may not speify a range that is within
  36. the bounds of the array. The Server shall return a partial result if some
  37. elements exist within the range.
  38. 2017-07-03 jpfr <julius.pfrommer at web.de>
  39. * Implement asynchronous service calls for the client
  40. All OPC UA services are asynchronous in nature. So several service calls can
  41. be made without waiting for a response first. Responess may come in a
  42. different ordering. The client takes a method pointer and a data pointer to
  43. perform an asynchronous callback on the request response.
  44. Synchronous service calls are still supported in the client. Asynchronous
  45. responses are processed in the background until the synchronous response (the
  46. client is waiting for) returns the control flow back to the user.
  47. 2017-06-26 janitza-thbe
  48. * Enable IPv6 in the networklayer plugin
  49. The server networklayer listens on several sockets for available networks and
  50. IP versions. IPv4 connections are still supported.
  51. The OPC Foundation ANSI C Stack before 2016 does not fully support IPv6. On
  52. Windows, the 'localhost' target is resolved to IPv6 by default. Old
  53. applications (e.g. the Conformance Testing Tools) need to connect to
  54. 127.0.0.1 instead of 'localhost' to force IPv4.
  55. 2017-06-16 jpfr <julius.pfrommer at web.de>
  56. * Require the AccessLevel bit UA_ACCESSLEVELMASK_READ for reading
  57. Set the bit by default when adding nodes for a smooth transition to the new
  58. API. This will change at a later point with an additional node settings
  59. argument for the AddNodes methods.
  60. 2017-05-03 pro <profanter at fortiss.org>
  61. * Array dimensions are UInt32 also for the highlevel client read service
  62. 2017-04-16 jpfr <julius.pfrommer at web.de>
  63. * Refactor UA_parseEndpointUrl to work with UA_String
  64. The output hostname and path now point into the original endpointUrl with an
  65. appropriate length.
  66. 2017-04-14 jpfr <julius.pfrommer at web.de>
  67. * Auto-instantiate only child nodes marked as mandatory (fixes #1004)