class WireWeakSyncClientImpl

Terminates the connection.

After calling `Close`, the client must not send any other requests.

Servers, after sending the status response, should close the connection

regardless of status and without sending an epitaph.

Closing the client end of the channel should be semantically equivalent

to calling `Close` without knowing when the close has completed or its

status.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.

DEPRECATED - Use `Node.GetAttributes` instead.

Allocates 96 bytes of message buffer on the stack. No heap allocation necessary.

DEPRECATED - Use `Node.UpdateAttributes` instead.

Allocates 104 bytes of message buffer on the stack. No heap allocation necessary.

[DEPRECATED - Use new GetFlags method instead.]

Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.

[DEPRECATED - Use new SetFlags method instead.]

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Queries the flags that apply to this node after it has been opened/created. This method does

not require any rights.

Note that the final set of flags that apply to the connection may differ from those

specified with the `fuchsia.io/Directory.Open` request used to create it:

- `Flags.PERM_INHERIT_*`: Only applies when determining connection rights.

- `Flags.PROTOCOL_*`: Only the protocol of the connection will be present.

- `Flags.FLAG_*`: Only applies when opening the resource, not part of the connection.

Allocates 56 bytes of message buffer on the stack. No heap allocation necessary.

Sets the flags that apply to this node after it has been opened. This method does not

require any rights.

Only `Flags.FILE_APPEND` is currently supported. Calling this method without any flags will

clear append mode.

Errors:

- `ZX_ERR_NOT_SUPPORTED`: The object does not support this feature or the specified flags.

- `ZX_ERR_INVALID_ARGS`: `flags` other than `Flags.FILE_APPEND` were specified.

Allocates 56 bytes of message buffer on the stack. No heap allocation necessary.

Query the filesystem for details specific to the filesystem and/or volume. If the current

volume has different settings or the storage is accounted seperately from the rest of the

filesystem that may be reported instead of filesystem-wide details.

Allocates 144 bytes of message buffer on the stack. No heap allocation necessary.

Acquires information about the node.

The attributes of a node should be stable, independent of the

specific protocol used to access it.

If a particular attribute is not applicable or not supported,

filesystems should leave the corresponding field absent.

+ `query` a bit-mask specifying which attributes to fetch. The server

should not return more than necessary.

- `attributes` the returned attributes.

This method requires the [`Rights.GET_ATTRIBUTES`] right.

Allocates 24 bytes of request buffer on the stack. Response is heap-allocated.

Updates information about the node.

+ `attributes` the presence of a table field in `attributes` indicates

the intent to update the corresponding attribute.

Returns `ZX_ERR_NOT_SUPPORTED` if the node does not support any of the specified attributes.

This method requires the [`Rights.UPDATE_ATTRIBUTES`] right.

Allocates 480 bytes of message buffer on the stack. No heap allocation necessary.

Synchronizes updates to the node to the underlying media, if it exists.

This method will return when the filesystem server has flushed the

relevant updates to the underlying media, but does not guarantee the

underlying media has persisted the information, nor that any information

is committed to hardware. Clients may use `Sync` to ensure ordering

between operations.

This method does not require any rights.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Get the value associated with the given attribute `name` for this node.

Attribute names have a maximum length of MAX_ATTRIBUTE_NAME. No

particular structure is imposed on them.

This method requires the [`Rights.GET_ATTRIBUTES`] right.

Allocates 288 bytes of request buffer on the stack. Response is heap-allocated.

Set the value for the given attribute `name` to `value` for this node.

The attribute name may exist, in which case the attribute is updated.

If the attribute doesn't exist, it is created. The name should have no

null bytes in it. If it does, ZX_ERR_INVALID_ARGS is returned.

This method requires the [`Rights.UPDATE_ATTRIBUTES`] right.

Allocates 32 bytes of response buffer on the stack. Request is heap-allocated.

Remove the specified extended attribute.

If the attribute doesn't exist, ZX_ERR_NOT_FOUND is returned.

This method requires the [`Rights.UPDATE_ATTRIBUTES`] right.

Allocates 320 bytes of message buffer on the stack. No heap allocation necessary.