node-opcua-file-transfer 2.73.1 → 2.76.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE CHANGED
@@ -1,6 +1,8 @@
1
1
  The MIT License (MIT)
2
2
 
3
- Copyright (c) 2014-2021 Etienne Rossignon
3
+ Copyright (c) 2022 Sterfive SAS - 833264583 RCS ORLEANS - France (https://www.sterfive.com)
4
+
5
+ Copyright (c) 2014-2022 Etienne Rossignon
4
6
 
5
7
  Permission is hereby granted, free of charge, to any person obtaining a copy of
6
8
  this software and associated documentation files (the "Software"), to deal in
@@ -1,68 +1,68 @@
1
- /// <reference types="node" />
2
- /**
3
- * @module node-opcua-file-transfer
4
- */
5
- import { Int32, UInt16, UInt32, UInt64 } from "node-opcua-basic-types";
6
- import { NodeId } from "node-opcua-nodeid";
7
- import { IBasicSession } from "node-opcua-pseudo-session";
8
- import { OpenFileMode } from "../open_mode";
9
- export { OpenFileMode } from "../open_mode";
10
- /**
11
- *
12
- *
13
- */
14
- export declare class ClientFile {
15
- static useGlobalMethod: boolean;
16
- fileHandle: number;
17
- protected session: IBasicSession;
18
- protected readonly fileNodeId: NodeId;
19
- private openMethodNodeId?;
20
- private closeMethodNodeId?;
21
- private setPositionNodeId?;
22
- private getPositionNodeId?;
23
- private readNodeId?;
24
- private writeNodeId?;
25
- private openCountNodeId?;
26
- private sizeNodeId?;
27
- constructor(session: IBasicSession, nodeId: NodeId);
28
- open(mode: OpenFileMode): Promise<number>;
29
- close(): Promise<void>;
30
- getPosition(): Promise<UInt64>;
31
- setPosition(position: UInt64 | UInt32): Promise<void>;
32
- read(bytesToRead: Int32): Promise<Buffer>;
33
- write(data: Buffer): Promise<void>;
34
- openCount(): Promise<UInt16>;
35
- size(): Promise<UInt64>;
36
- protected extractMethodsIds(): Promise<void>;
37
- protected ensureInitialized(): Promise<void>;
38
- }
39
- /**
40
- * 5.2.10 UserRolePermissions
41
- *
42
- * The optional UserRolePermissions Attribute specifies the Permissions that apply to a Node for
43
- * all Roles granted to current Session. The value of the Attribute is an array of
44
- * RolePermissionType Structures (see Table 8).
45
- * Clients may determine their effective Permissions by logically ORing the Permissions for each
46
- * Role in the array.
47
- * The value of this Attribute is derived from the rules used by the Server to map Sessions to
48
- * Roles. This mapping may be vendor specific or it may use the standard Role model defined in 4.8.
49
- * This Attribute shall not be writeable.
50
- * If not specified, the value of DefaultUserRolePermissions Property from the Namespace
51
- * Metadata Object associated with the Node is used instead. If the NamespaceMetadata Object
52
- * does not define the Property or does not exist, then the Server does not publish any information
53
- * about Roles mapped to the current Session.
54
- *
55
- *
56
- * 5.2.11 AccessRestrictions
57
- * The optional AccessRestrictions Attribute specifies the AccessRestrictions that apply to a Node.
58
- * Its data type is defined in 8.56. If a Server supports AccessRestrictions for a particular
59
- * Namespace it adds the DefaultAccessRestrictions Property to the NamespaceMetadata Object
60
- * for that Namespace (see Figure 8). If a particular Node in the Namespace needs to override
61
- * the default value the Server adds the AccessRestrictions Attribute to the Node.
62
- * If a Server implements a vendor specific access restriction model for a Namespace, it does not
63
- * add the DefaultAccessRestrictions Property to the NamespaceMetadata Object.
64
- *
65
- *
66
- * DefaultAccessRestrictions
67
- *
68
- */
1
+ /// <reference types="node" />
2
+ /**
3
+ * @module node-opcua-file-transfer
4
+ */
5
+ import { Int32, UInt16, UInt32, UInt64 } from "node-opcua-basic-types";
6
+ import { NodeId } from "node-opcua-nodeid";
7
+ import { IBasicSession } from "node-opcua-pseudo-session";
8
+ import { OpenFileMode } from "../open_mode";
9
+ export { OpenFileMode } from "../open_mode";
10
+ /**
11
+ *
12
+ *
13
+ */
14
+ export declare class ClientFile {
15
+ static useGlobalMethod: boolean;
16
+ fileHandle: number;
17
+ protected session: IBasicSession;
18
+ protected readonly fileNodeId: NodeId;
19
+ private openMethodNodeId?;
20
+ private closeMethodNodeId?;
21
+ private setPositionNodeId?;
22
+ private getPositionNodeId?;
23
+ private readNodeId?;
24
+ private writeNodeId?;
25
+ private openCountNodeId?;
26
+ private sizeNodeId?;
27
+ constructor(session: IBasicSession, nodeId: NodeId);
28
+ open(mode: OpenFileMode): Promise<number>;
29
+ close(): Promise<void>;
30
+ getPosition(): Promise<UInt64>;
31
+ setPosition(position: UInt64 | UInt32): Promise<void>;
32
+ read(bytesToRead: Int32): Promise<Buffer>;
33
+ write(data: Buffer): Promise<void>;
34
+ openCount(): Promise<UInt16>;
35
+ size(): Promise<UInt64>;
36
+ protected extractMethodsIds(): Promise<void>;
37
+ protected ensureInitialized(): Promise<void>;
38
+ }
39
+ /**
40
+ * 5.2.10 UserRolePermissions
41
+ *
42
+ * The optional UserRolePermissions Attribute specifies the Permissions that apply to a Node for
43
+ * all Roles granted to current Session. The value of the Attribute is an array of
44
+ * RolePermissionType Structures (see Table 8).
45
+ * Clients may determine their effective Permissions by logically ORing the Permissions for each
46
+ * Role in the array.
47
+ * The value of this Attribute is derived from the rules used by the Server to map Sessions to
48
+ * Roles. This mapping may be vendor specific or it may use the standard Role model defined in 4.8.
49
+ * This Attribute shall not be writeable.
50
+ * If not specified, the value of DefaultUserRolePermissions Property from the Namespace
51
+ * Metadata Object associated with the Node is used instead. If the NamespaceMetadata Object
52
+ * does not define the Property or does not exist, then the Server does not publish any information
53
+ * about Roles mapped to the current Session.
54
+ *
55
+ *
56
+ * 5.2.11 AccessRestrictions
57
+ * The optional AccessRestrictions Attribute specifies the AccessRestrictions that apply to a Node.
58
+ * Its data type is defined in 8.56. If a Server supports AccessRestrictions for a particular
59
+ * Namespace it adds the DefaultAccessRestrictions Property to the NamespaceMetadata Object
60
+ * for that Namespace (see Figure 8). If a particular Node in the Namespace needs to override
61
+ * the default value the Server adds the AccessRestrictions Attribute to the Node.
62
+ * If a Server implements a vendor specific access restriction model for a Namespace, it does not
63
+ * add the DefaultAccessRestrictions Property to the NamespaceMetadata Object.
64
+ *
65
+ *
66
+ * DefaultAccessRestrictions
67
+ *
68
+ */