Abstract: A method for supporting files names in a storage system, the method may include receiving a first protocol request for creating an object having a requested object name that comprises one or more sets of slashes, wherein the first protocol does not use the one or more sets as hierarchy separators; wherein each set of slashes comprises one or more consecutive slashes; determining a role of each set of the one or more sets in a second protocol that uses slashes as hierarchy separators; and generating a path name for accessing the object, when using either one of the first and second protocols, wherein the generating is based on the requested object name and the role of each set.

Abstract: A method for supporting files names in a storage system, the method may include receiving a first protocol request for creating an object having a requested object name that comprises one or more sets of slashes, wherein the first protocol does not use the one or more sets as hierarchy separators; wherein each set of slashes comprises one or more consecutive slashes; determining a role of each set of the one or more sets in a second protocol that uses slashes as hierarchy separators; and generating a path name for accessing the object, when using either one of the first and second protocols, wherein the generating is based on the requested object name and the role of each set.

Abstract: For preventing implementation errors due to misconfigured host applications, a storage controller provisions a storage destination with a capability identifier configured to indicate that the storage destination mandates atomic write operations. The storage controller also receives a write request for the storage destination from host application, and rejects, in response to the received request including a non-atomic write operation, the non-atomic write request.

Abstract: Embodiments for discovering read failures in a data storage system. Data read from underlying media of the data storage system is validated by initializing a prefix of a buffer used to read the data with a first sequence of bytes of a predefined number. The first sequence of bytes is compared to a sequence of actual bytes of the data read into the buffer. When the first sequence of bytes returns an equal value to the sequence of the actual bytes of the data read, a second sequence of bytes of the predefined number is generated and compared to a subsequent data read to determine the validity.

Abstract: For preventing implementation errors due to misconfigured host applications, a storage controller provisions a storage destination with a capability identifier configured to indicate that the storage destination mandates atomic write operations. The storage controller also receives a write request for the storage destination from host application, and rejects, in response to the received request including a non-atomic write operation, the non-atomic write request.

Abstract: Embodiments for discovering read failures in a data storage system. Data read from underlying media of the data storage system is validated by initializing a prefix of a buffer used to read the data with a first sequence of bytes of a predefined number. The first sequence of bytes is compared to a sequence of actual bytes of the data read into the buffer. When the first sequence of bytes returns an equal value to the sequence of the actual bytes of the data read, a second sequence of bytes of the predefined number is generated and compared to a subsequent data read to determine the validity.

Abstract: A method and system for a dial plan parser includes a state machine configured upon a dial plan to which is applied call signaling data, and a call routing module/switch to transfer a call to a next point.

Abstract: A method and system for a dial plan parser includes a state machine configured upon a dial plan to which is applied call signaling data, and a call routing module/switch to transfer a call to a next point.

Abstract: A method is provided, for remotely updating information to, and controlling, a network appliance, which resides in a private location behind a network address translator (“NAT”), from a remote update server (“RUS”) that resides in a public location, the Internet Protocol (“IP”) address of, and a destination port number on, the RUS being known to the network appliance. The NAT may intermittently forward from the network appliance initialization messages that may be received at the RUS via its destination port. Responsive to the initialization messages being received at the RUS, the RUS may determine the source IP address and port number on the NAT from which the messages were received and send update data and/or control signal(s) via the destination port to the port number on the NAT.