* This class is designed to manage FTP authentication details for different paths.
 */
public class FtpAuthenticationHolder {
    List<FtpAuthentication> authenticationList = new ArrayList<>();

    /**
     * Constructs a new FtpAuthenticationHolder.
     */
    public FtpAuthenticationHolder() {
        // Default constructor
    }

    /**
     * Adds an FtpAuthentication object to the holder.

 * acquisition or release of byte-range locks.
 *
 * @author mbechler
 *
 */
public class Smb2LockResponse extends ServerMessageBlock2Response {

    /**
     * Constructs an SMB2 lock response with the given configuration.
     *
     * @param config the configuration for this response
     */
    public Smb2LockResponse(final Configuration config) {
        super(config);
    }

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

    private static final int SMB_SHARE_IS_IN_DFS = 0x0002;

    private boolean supportSearchBits, shareIsInDfs;
    private String service;
    private String nativeFileSystem = "";

    /**
     * Constructs a tree connect AndX response.
     *
     * @param config the configuration to use
     * @param andx the next command in the AndX chain, or null
     */

 * Converter for numbers.
 *
 * @author higa
 */
public class NumberConverter implements Converter {

    /**
     * The pattern for numbers.
     */
    protected String pattern;

    /**
     * Constructs an instance.
     *
     * @param pattern
     *            the pattern for numbers
     */
    public NumberConverter(final String pattern) {
        assertArgumentNotEmpty("pattern", pattern);

 *
 * @author higa
 */
public class TimestampConverter implements Converter {

    /**
     * The pattern for the date and time.
     */
    protected String pattern;

    /**
     * Constructs an instance.
     *
     * @param pattern
     *            the pattern for date and time
     */
    public TimestampConverter(final String pattern) {
        assertArgumentNotEmpty("pattern", pattern);