/home/kueuepay/public_html/vendor/maennchen/zipstream-php/src/Option/Archive.php
<?php

declare(strict_types=1);

namespace ZipStream\Option;

use Psr\Http\Message\StreamInterface;

final class Archive
{
    public const DEFAULT_DEFLATE_LEVEL = 6;

    /**
     * @var string
     */
    private $comment = '';

    /**
     * Size, in bytes, of the largest file to try
     * and load into memory (used by
     * addFileFromPath()).  Large files may also
     * be compressed differently; see the
     * 'largeFileMethod' option. Default is ~20 Mb.
     *
     * @var int
     */
    private $largeFileSize = 20 * 1024 * 1024;

    /**
     * How to handle large files.  Legal values are
     * Method::STORE() (the default), or
     * Method::DEFLATE(). STORE sends the file
     * raw and is significantly
     * faster, while DEFLATE compresses the file
     * and is much, much slower. Note that DEFLATE
     * must compress the file twice and is extremely slow.
     *
     * @var Method
     */
    private $largeFileMethod;

    /**
     * Boolean indicating whether or not to send
     * the HTTP headers for this file.
     *
     * @var bool
     */
    private $sendHttpHeaders = false;

    /**
     * The method called to send headers
     *
     * @var Callable
     */
    private $httpHeaderCallback = 'header';

    /**
     * Enable Zip64 extension, supporting very large
     * archives (any size > 4 GB or file count > 64k)
     *
     * @var bool
     */
    private $enableZip64 = true;

    /**
     * Enable streaming files with single read where
     * general purpose bit 3 indicates local file header
     * contain zero values in crc and size fields,
     * these appear only after file contents
     * in data descriptor block.
     *
     * @var bool
     */
    private $zeroHeader = false;

    /**
     * Enable reading file stat for determining file size.
     * When a 32-bit system reads file size that is
     * over 2 GB, invalid value appears in file size
     * due to integer overflow. Should be disabled on
     * 32-bit systems with method addFileFromPath
     * if any file may exceed 2 GB. In this case file
     * will be read in blocks and correct size will be
     * determined from content.
     *
     * @var bool
     */
    private $statFiles = true;

    /**
     * Enable flush after every write to output stream.
     * @var bool
     */
    private $flushOutput = false;

    /**
     * HTTP Content-Disposition.  Defaults to
     * 'attachment', where
     * FILENAME is the specified filename.
     *
     * Note that this does nothing if you are
     * not sending HTTP headers.
     *
     * @var string
     */
    private $contentDisposition = 'attachment';

    /**
     * Note that this does nothing if you are
     * not sending HTTP headers.
     *
     * @var string
     */
    private $contentType = 'application/x-zip';

    /**
     * @var int
     */
    private $deflateLevel = 6;

    /**
     * @var StreamInterface|resource
     */
    private $outputStream;

    /**
     * Options constructor.
     */
    public function __construct()
    {
        $this->largeFileMethod = Method::STORE();
        $this->outputStream = fopen('php://output', 'wb');
    }

    public function getComment(): string
    {
        return $this->comment;
    }

    public function setComment(string $comment): void
    {
        $this->comment = $comment;
    }

    public function getLargeFileSize(): int
    {
        return $this->largeFileSize;
    }

    public function setLargeFileSize(int $largeFileSize): void
    {
        $this->largeFileSize = $largeFileSize;
    }

    public function getLargeFileMethod(): Method
    {
        return $this->largeFileMethod;
    }

    public function setLargeFileMethod(Method $largeFileMethod): void
    {
        $this->largeFileMethod = $largeFileMethod;
    }

    public function isSendHttpHeaders(): bool
    {
        return $this->sendHttpHeaders;
    }

    public function setSendHttpHeaders(bool $sendHttpHeaders): void
    {
        $this->sendHttpHeaders = $sendHttpHeaders;
    }

    public function getHttpHeaderCallback(): callable
    {
        return $this->httpHeaderCallback;
    }

    public function setHttpHeaderCallback(callable $httpHeaderCallback): void
    {
        $this->httpHeaderCallback = $httpHeaderCallback;
    }

    public function isEnableZip64(): bool
    {
        return $this->enableZip64;
    }

    public function setEnableZip64(bool $enableZip64): void
    {
        $this->enableZip64 = $enableZip64;
    }

    public function isZeroHeader(): bool
    {
        return $this->zeroHeader;
    }

    public function setZeroHeader(bool $zeroHeader): void
    {
        $this->zeroHeader = $zeroHeader;
    }

    public function isFlushOutput(): bool
    {
        return $this->flushOutput;
    }

    public function setFlushOutput(bool $flushOutput): void
    {
        $this->flushOutput = $flushOutput;
    }

    public function isStatFiles(): bool
    {
        return $this->statFiles;
    }

    public function setStatFiles(bool $statFiles): void
    {
        $this->statFiles = $statFiles;
    }

    public function getContentDisposition(): string
    {
        return $this->contentDisposition;
    }

    public function setContentDisposition(string $contentDisposition): void
    {
        $this->contentDisposition = $contentDisposition;
    }

    public function getContentType(): string
    {
        return $this->contentType;
    }

    public function setContentType(string $contentType): void
    {
        $this->contentType = $contentType;
    }

    /**
     * @return StreamInterface|resource
     */
    public function getOutputStream()
    {
        return $this->outputStream;
    }

    /**
     * @param StreamInterface|resource $outputStream
     */
    public function setOutputStream($outputStream): void
    {
        $this->outputStream = $outputStream;
    }

    /**
     * @return int
     */
    public function getDeflateLevel(): int
    {
        return $this->deflateLevel;
    }

    /**
     * @param int $deflateLevel
     */
    public function setDeflateLevel(int $deflateLevel): void
    {
        $this->deflateLevel = $deflateLevel;
    }
}
FAQ

FAQ

1. What is the Kueue Pay Payment Gateway?

The Kueue Pay Payment Gateway is an innovative technology that facilitates seamless and secure transactions between merchants and their customers. It enables businesses to accept debit and credit card payments both online and in physical stores.

2. How does the Kueue Pay Payment Gateway work?

The Kueue Pay Payment Gateway acts as a bridge between a merchant’s website or point-of-sale system and the payment processing network. It securely transmits payment information, authorizes transactions, and provides real-time status updates.

3. What is the advantage of using Kueue Pay’s Developer API?

The Kueue Pay Developer API empowers developers and entrepreneurs to integrate the Kueue Pay Payment Gateway directly into their websites or applications. This streamlines the payment process for customers and provides businesses with a customizable and efficient payment solution.

4. How can I access the Kueue Pay Developer API?

To access the Kueue Pay Developer API, you need to sign up for a developer account on our platform. Once registered, you’ll receive an API key that you can use to authenticate your API requests.

5. What types of transactions can I handle with the Kueue Pay Developer API?

The Kueue Pay Developer API allows you to initiate payments, check the status of payments, and process refunds. You can create a seamless payment experience for your customers while maintaining control over transaction management.

6. Is the Kueue Pay Developer API suitable for my business size and industry?

Yes, the Kueue Pay Developer API is designed to accommodate businesses of varying sizes and industries. Whether you’re a small online store or a large enterprise, our API can be tailored to fit your specific payment needs.

7. How user-friendly is the Kueue Pay Developer API integration process?

The Kueue Pay Developer API is designed with simplicity and ease of use in mind. Our comprehensive documentation, code samples, and developer support resources ensure a smooth integration process for any web platform.

8. Are there any fees associated with using the Kueue Pay Payment Gateway and API?

We offer competitive pricing plans for using the Kueue Pay Payment Gateway and Developer API. Details about fees and pricing tiers can be found on our developer portal.

9. Can I customize the payment experience for my customers using the Kueue Pay API?

Absolutely, the Kueue Pay Developer API offers customization options that allow you to tailor the payment experience to match your brand and user interface. You can create a seamless and cohesive payment journey for your customers.

10. What kind of support is available if I encounter issues during API integration?

We provide dedicated developer support to assist you with any issues or questions you may have during the API integration process. Reach out to our support team at developersupport@NFCPay.com for prompt assistance.

Remember, our goal is to empower your business with a robust and efficient payment solution. If you have any additional questions or concerns, feel free to explore our developer portal or contact our support team.