Classes, interfaces and traits

AuthProvider

User-facing interface for authenticating users.

« More »

ChainAuth

Chain several auth providers as if they were one. This is useful for cases where one want to authenticate across several providers, for example, database and fallback to passwd file.

« More »

HashingAlgorithm

Hashing Algorithm. A common interface to interact with any system provided algorithms.

« More »

HashingStrategy

Hashing Strategy manager.

This class will load system provided hashing strategies and algorithms.

« More »

User

Represents an authenticates User and contains operations to authorise the user.

Please consult the documentation for a detailed explanation.

« More »

VertxContextPRNG

A secure non blocking random number generator isolated to the current context. The PRNG is bound to the vert.x context and setup to close when the context shuts down.

When applicable, use of VertxContextPRNG rather than create new PRNG objects is helpful to keep the system entropy usage to the minimum avoiding potential blocking across the application.

The use of VertxContextPRNG is particularly appropriate when multiple handlers use random numbers.

« More »

Classes, interfaces and traits

HtdigestAuth

An extension of AuthProvider which is using .htdigest file as store

« More »

Classes, interfaces and traits

HtpasswdAuth

An extension of AuthProvider which is using htpasswd file as store

« More »

Classes, interfaces and traits

JDBCAuth

Factory interface for creating @see \io\vertx\jphp\ext\auth\AuthProvider instances that use the Vert.x JDBC client.

By default the hashing strategy is SHA-512. If you're already running in production this is backwards compatible, however for new deployments or security upgrades it is recommended to use the PBKDF2 strategy as it is the current OWASP recommendation for password storage.

« More »

JDBCHashStrategy

Determines how the hashing is computed in the implementation

You can implement this to provide a different hashing strategy to the default.

« More »

Classes, interfaces and traits

JWTAuth

Factory interface for creating JWT based @see \io\vertx\jphp\ext\auth\AuthProvider instances.

« More »

Classes, interfaces and traits

HashStrategy

Determines how the hashing is computed in the implementation You can implement this to provide a different hashing strategy to the default.

« More »

MongoAuth

An extension of AuthProvider which is using as store

« More »

Classes, interfaces and traits

AccessToken

AccessToken extension to the User interface

« More »

KeycloakHelper

Helper class for processing Keycloak principal.

« More »

OAuth2Auth

Factory interface for creating OAuth2 based @see \io\vertx\jphp\ext\auth\AuthProvider instances.

« More »

OAuth2RBAC

Functional interface that allows users to implement custom RBAC verifiers for OAuth2/OpenId Connect.

Users are to implement the isAuthorized method to verify authorities. For provides that do not export the permissions/roles in the token, this interface allows you to communicate with 3rd party services such as graph APIs to collect the required data.

The contract is that once an authority is checked for a given user, it's value is cached during the execution of the request. If a user is stored to a persistent storage, or the token is introspected, the cache is cleared and a new call will be handled to the implementation.

« More »

OAuth2Response

A response from a fetch request.

This class represents a secure response from a Oauth2 fetch call.

A fetch is a simplified HTTP response from a protected resource.

« More »

Classes, interfaces and traits

AzureADAuth

Simplified factory to create an for Azure AD.

« More »

BoxAuth

Simplified factory to create an for box.com.

« More »

CloudFoundryAuth

Simplified factory to create an for CloudFoundry UAA.

« More »

DropboxAuth

Simplified factory to create an for Dropbox.

« More »

FacebookAuth

Simplified factory to create an for Facebook.

« More »

FoursquareAuth

Simplified factory to create an for Foursquare.

« More »

GithubAuth

Simplified factory to create an for Github.

« More »

GoogleAuth

Simplified factory to create an @see \io\vertx\jphp\ext\auth\oauth2\OAuth2Auth for Google.

« More »

HerokuAuth

Simplified factory to create an for Heroku.

« More »

InstagramAuth

Simplified factory to create an for Instagram.

« More »

KeycloakAuth

Simplified factory to create an for Keycloak.

« More »

LinkedInAuth

Simplified factory to create an for LinkedIn.

« More »

LiveAuth

Simplified factory to create an for live.com Services.

« More »

MailchimpAuth

Simplified factory to create an for Mailchimp.

« More »

OpenIDConnectAuth

Simplified factory to create an @see \io\vertx\jphp\ext\auth\oauth2\OAuth2Auth for OpenID Connect.

« More »

SalesforceAuth

Simplified factory to create an for Salesforce.

« More »

ShopifyAuth

Simplified factory to create an for Shopify.

« More »

SoundcloudAuth

Simplified factory to create an for SoundCloud.

« More »

StripeAuth

Simplified factory to create an for Stripe.

« More »

TwitterAuth

Simplified factory to create an for Twitter.

« More »

Classes, interfaces and traits

KeycloakRBAC

Implementation of the Keycloak RBAC handler.

« More »

MicroProfileRBAC

Implementation of the Microprofile MP-JWT 1.1 RBAC based on the access token groups key.

« More »

Classes, interfaces and traits

ShiroAuth

Factory interface for creating Apache Shiro based @see \io\vertx\jphp\ext\auth\AuthProvider instances.

« More »

Classes, interfaces and traits

BaseBridgeEvent

Represents an event that occurs on the event bus bridge.

Please consult the documentation for a full explanation.

« More »

Classes, interfaces and traits

ConsulClient

A Vert.x service used to interact with Consul.

« More »

Watch

Watches are a way of specifying a view of data (e.g. list of nodes, KV pairs, health checks) which is monitored for updates. When an update is detected, an <code>Handler</code> with <code>AsyncResult</code> is invoked.

As an example, you could watch the status of health checks and notify when a check is critical.

« More »

WatchResult

« More »

Classes, interfaces and traits

MetricsService

The metrics service mainly allows to return a snapshot of measured objects.

« More »

Classes, interfaces and traits

BridgeEvent

Represents an event that occurs on the event bus bridge.

Please consult the documentation for a full explanation.

« More »

TcpEventBusBridge

TCP EventBus bridge for Vert.x

« More »

Classes, interfaces and traits

HealthCheckHandler

A Vert.x Web handler on which you register health check procedure. It computes the outcome status (`UP` or `DOWN`)

. When the handler process a HTTP request, it computes the global outcome and build a HTTP response as follows:

  • 204 - status is `UP` but no procedures installed (no payload)
  • 200 - status is `UP`, the payload contains the result of the installed procedures
  • 503 - status is `DOWN`, the payload contains the result of the installed procedures
  • 500 - status is `DOWN`, the payload contains the result of the installed procedures, one of the procedure has failed
« More »

HealthChecks

« More »

Classes, interfaces and traits

JDBCClient

An asynchronous client interface for interacting with a JDBC compliant database

« More »

Classes, interfaces and traits

MailAttachment

Represent a mail attachment that can be used in a MailMessage.

« More »

MailClient

SMTP mail client for Vert.x <p> A simple asynchronous API for sending mails from Vert.x applications

« More »

Classes, interfaces and traits

MongoClient

A Vert.x service used to interact with MongoDB server instances.

Some of the operations might change _id field of passed document.

« More »

Classes, interfaces and traits

Shell

An interactive session between a consumer and a shell.

« More »

ShellServer

The shell server.<p/>

A shell server is associated with a collection of : the @see \io\vertx\jphp\ext\shell\ShellServer::registerTermServer method registers a term server. Term servers life cycle are managed by this server.

When a receives an incoming connection, a instance is created and associated with this connection.

The @see \io\vertx\jphp\ext\shell\ShellServer::createShell method can be used to create instance for testing purposes.

« More »

ShellService

The shell service, provides a remotely accessible shell available via Telnet or SSH according to the

« More »

Classes, interfaces and traits

CliToken

A parsed token in the command line interface.

« More »

Completion

The completion object

« More »

Classes, interfaces and traits

Command

A Vert.x Shell command, it can be created from any language using the @see \io\vertx\jphp\ext\shell\command\CommandBuilder::command or from a Java class using @see \io\vertx\jphp\ext\shell\command\Command::create

« More »

CommandBuilder

A build for Vert.x Shell command.

« More »

CommandProcess

The command process provides interaction with the process of the command provided by Vert.x Shell.

« More »

CommandRegistry

A registry that contains the commands known by a shell.<p/>

It is a mutable command resolver.

« More »

CommandResolver

A resolver for commands, so the shell can discover commands.

« More »

Classes, interfaces and traits

Session

A shell session.

« More »

Classes, interfaces and traits

Job

A job executed in a @see \io\vertx\jphp\ext\shell\system\JobController, grouping one or several process.<p/>

The job life cycle can be controlled with the @see \io\vertx\jphp\ext\shell\system\Job::run, @see \io\vertx\jphp\ext\shell\system\Job::resume and @see \io\vertx\jphp\ext\shell\system\Job::suspend and @see \io\vertx\jphp\ext\shell\system\Job::interrupt methods.

« More »

JobController

The job controller.<p/>

« More »

Process

A process managed by the shell.

« More »

Classes, interfaces and traits

Pty

A pseudo terminal used for controlling a @see \io\vertx\jphp\ext\shell\term\Tty. This interface acts as a pseudo terminal master, @see \io\vertx\jphp\ext\shell\term\Pty::slave returns the assocated slave pseudo terminal.

« More »

SignalHandler

« More »

SockJSTermHandler

« More »

TermServer

A server for terminal based applications.

« More »

Tty

Provide interactions with the Shell TTY.

« More »

Classes, interfaces and traits

SQLClient

A common asynchronous client interface for interacting with SQL compliant database

« More »

SQLConnection

Represents a connection to a SQL database

« More »

SQLOperations

Represents a SQL query interface to a database

« More »

SQLRowStream

A ReadStream of Rows from the underlying RDBMS. This class follows the ReadStream semantics and will automatically close the underlying resources if all returned rows are returned. For cases where the results are ignored before the full processing of the returned rows is complete the close method **MUST** be called in order to release underlying resources.

The interface is minimal in order to support all SQL clients not just JDBC.

« More »

Classes, interfaces and traits

Acknowledgement

Structure passed to acknowledgement handler called when a <code>ACK</code> or <code>NACK</code> frame is received. The handler receives an instance of @see \io\vertx\jphp\ext\stomp\Acknowledgement with the subscription @see \io\vertx\jphp\ext\stomp\Frame and the impacted messages. The list of messages depends on the type of acknowledgment used by the subscription.

Subscriptions using the client mode receives all messages that were waiting for acknowledgment that were sent before the acknowledged messages. The list also contains the acknowledged message. This is a cumulative acknowledgement. Subscriptions using the client-individual mode receives a singleton list containing only the acknowledged message.

« More »

Destination

Represents a STOMP destination.

Depending on the implementation, the message delivery is different. Queue are sending message to only one subscribers, while topics are broadcasting the message to all subscribers.

Implementations must be thread-safe.

« More »

DestinationFactory

Interface implemented to customize the destination creation.

« More »

Frames

Utility methods to build common @see \io\vertx\jphp\ext\stomp\Frames. It defines a non-STOMP frame (<code>PING</code>) that is used for heartbeats. When such frame is written on the wire it is just the <code>0</code> byte.

This class is thread-safe.

« More »

ServerFrame

Structure passed to server handler when receiving a frame. It provides a reference on the received @see \io\vertx\jphp\ext\stomp\Frame but also on the @see \io\vertx\jphp\ext\stomp\StompServerConnection.

« More »

StompClient

Defines a STOMP client.

« More »

StompClientConnection

Once a connection to the STOMP server has been made, client receives a @see \io\vertx\jphp\ext\stomp\StompClientConnection, that let send and receive STOMP frames.

« More »

StompServer

Defines a STOMP server. STOMP servers delegates to a @see \io\vertx\jphp\ext\stomp\StompServerHandler that let customize the behavior of the server. By default, it uses a handler compliant with the STOMP specification, but let you change anything.

« More »

StompServerConnection

Class representing a connection between a STOMP client a the server. It keeps a references on the client socket, so let write to this socket.

« More »

StompServerHandler

STOMP server handler implements the behavior of the STOMP server when a specific event occurs. For instance, if let customize the behavior when specific STOMP frames arrives or when a connection is closed. This class has been designed to let you customize the server behavior. The default implementation is compliant with the STOMP specification. In this default implementation, not acknowledge frames are dropped.

« More »

Classes, interfaces and traits

Async

An asynchronous exit point for a test.<p/>

« More »

Completion

A completion object that emits completion notifications either <i>succeeded</i> or <i>failed</i>.

« More »

TestCase

A test case object can be used to create a single test.

« More »

TestCompletion

This object provides callback-ability for the end of a test suite, the completion <i>succeeds</i> when all tests pass otherwise it fails.

« More »

TestContext

The test context is used for performing test assertions and manage the completion of the test. This context is provided by <i>vertx-unit</i> as argument of the test case.

« More »

TestSuite

A named suite of test cases that are executed altogether. The suite suite is created with the @see \io\vertx\jphp\ext\unit\TestSuite::create and the returned suite contains initially no tests.<p/>

The suite can declare a callback before the suite with @see \io\vertx\jphp\ext\unit\TestSuite::before or after the suite with @see \io\vertx\jphp\ext\unit\TestSuite::after.

The suite can declare a callback before each test with @see \io\vertx\jphp\ext\unit\TestSuite::beforeEach or after each test with @see \io\vertx\jphp\ext\unit\TestSuite::afterEach.

Each test case of the suite is declared by calling the @see \io\vertx\jphp\ext\unit\TestSuite::test method.

« More »

Classes, interfaces and traits

EventBusCollector

The event bus collector listen to events on the Vert.x event bus and translate them into reports.

« More »

Classes, interfaces and traits

Failure

A failure provides the details of a failure that happened during the execution of a test case.<p/>

The failure can be:

  • an assertion failure: an assertion failed
  • an error failure: an expected error occured
« More »

TestCaseReport

Report the execution of a test case.

« More »

TestResult

The result of a test.

« More »

TestSuiteReport

The test suite reports is basically a stream of events reporting the test suite execution.

« More »

Classes, interfaces and traits

FileUpload

Represents a file-upload from an HTTP multipart form submission.

« More »

LanguageHeader

A parsed language header.

Delivers a more direct access to the individual elements of the header it represents

« More »

Locale

« More »

MIMEHeader

« More »

ParsedHeaderValue

« More »

ParsedHeaderValues

A container with the request's headers that are meaningful enough to be parsed Contains: <ul> <li>Accept -> MIME header, parameters and sortable</li> <li>Accept-Charset -> Parameters and sortable</li> <li>Accept-Encoding -> Parameters and sortable</li> <li>Accept-Language -> Parameters and sortable</li> <li>Content-Type -> MIME header and parameters</li> </ul>

« More »

Route

A route is a holder for a set of criteria which determine whether an HTTP request or failure should be routed to a handler.

« More »

Router

A router receives request from an @see \io\vertx\jphp\core\http\HttpServer and routes it to the first matching

« More »

RoutingContext

Represents the context for the handling of a request in Vert.x-Web.

A new instance is created for each HTTP request that is received in the of the router.

The same instance is passed to any matching request or failure handlers during the routing of the request or failure.

The context provides access to the and and allows you to maintain arbitrary data that lives for the lifetime of the context. Contexts are discarded once they have been routed to the handler for the request.

The context also provides access to the @see \io\vertx\jphp\ext\web\Session, cookies and body for the request, given the correct handlers in the application.

If you use the internal error handler

« More »

Session

Represents a browser session.

Sessions persist between HTTP requests for a single browser session. They are deleted when the browser is closed, or they time-out. Session cookies are used to maintain sessions using a secure UUID.

Sessions can be used to maintain data for a browser session, e.g. a shopping basket.

The context must have first been routed to a @see \io\vertx\jphp\ext\web\handler\SessionHandler for sessions to be available.

« More »

Classes, interfaces and traits

RequestParameter

Request parameter holder

« More »

RequestParameters

Container for request parameters

« More »

Classes, interfaces and traits

HTTPOperationRequestValidationHandler

Base interface for HTTP request validation with API specification

« More »

RouterFactory

Main interface for Design Driven Router factory Author: Francesco Guardiani @slinkydeveloper

« More »

Classes, interfaces and traits

OpenAPI3RequestValidationHandler

« More »

OpenAPI3RouterFactory

Interface for OpenAPI3RouterFactory. <br/> To add an handler, use @see \io\vertx\jphp\ext\web\api\contract\openapi3\OpenAPI3RouterFactory::addHandlerByOperationId<br/> Usage example: <pre> <code>OpenAPI3RouterFactory.create(vertx, "src/resources/spec.yaml", asyncResult -> { if (!asyncResult.succeeded()) { // IO failure or spec invalid</code> else { OpenAPI3RouterFactory routerFactory = asyncResult.result(); routerFactory.addHandlerByOperationId("operation_id", routingContext -> { // Do something }, routingContext -> { // Do something with failure handler }); Router router = routerFactory.getRouter(); } }); } </pre> <br/> Handlers are loaded in this order:<br/> <ol> <li>Body handler (Customizable with </li> <li>Custom global handlers configurable with </li> <li>Global security handlers defined in upper spec level</li> <li>Operation specific security handlers</li> <li>Generated validation handler</li> <li>User handlers or "Not implemented" handler</li> </ol>

« More »

Classes, interfaces and traits

ContainerDeserializer

Interface that define methods for deserialization of array and objects

« More »

CustomValidator

This interface is used to add custom <b>synchronous</b> functions inside validation process. You can add it in

« More »

HTTPRequestValidationHandler

An interface for add HTTP Request validation. This class can validate parameters inside query, path, headers an body (watch below) <br/> You can assign multiple body type at the same time(for example a JSON schema together with a XML schema). This interface support: <ul> <li>application/x-www-form-urlencoded</li> <li>multipart/form-data</li> <li>application/xml</li> <li>application/json</li> </ul> Also you can add a form parameter for validation without care about content type of your request. For form parameters this interface support both "multipart/form-data" and "application/x-www-form-urlencoded" <br/> This interface allow extra parameters in the request, so it doesn't care if in a request there's a parameter without a specified validation rule <br/> If a parameter is flagged as an array, it will be validated also if the size of array is 1 element

« More »

ParameterTypeValidator

Interface for declaration of method for validate a specific parameter type.<br/> If you want to implement your own type validator, you need only to implement

« More »

ParameterValidationRule

This function is an inner wrapper for ParameterTypeValidator inside ValidationHandler parameter maps. <b>Don't instantiate this class</b>, if you want to add custom ParameterTypeValidator to a parameter use functions in

« More »

ValidationHandler

Base interface for validation.

For basic HTTP Request Validator, use @see \io\vertx\jphp\ext\web\api\validation\HTTPRequestValidationHandler

« More »

Classes, interfaces and traits

HttpResponse

An HTTP response.

The usual HTTP response attributes are available:

  • @see \io\vertx\jphp\ext\web\client\HttpResponse::statusCode the HTTP status code
  • @see \io\vertx\jphp\ext\web\client\HttpResponse::statusMessage the HTTP status message
  • @see \io\vertx\jphp\ext\web\client\HttpResponse::headers the HTTP headers
  • @see \io\vertx\jphp\ext\web\client\HttpResponse::version the HTTP version

The body of the response is returned by @see \io\vertx\jphp\ext\web\client\HttpResponse::body decoded as the format specified by the @see \io\vertx\jphp\ext\web\codec\BodyCodec that built the response.

Keep in mind that using this HttpResponse impose to fully buffer the response body and should be used for payload that can fit in memory.

« More »

WebClient

An asynchronous HTTP / HTTP/2 client called <code>WebClient</code>.

The web client makes easy to do HTTP request/response interactions with a web server, and provides advanced features like:

  • Json body encoding / decoding
  • request/response pumping
  • error handling

The web client does not deprecate the , it is actually based on it and therefore inherits its configuration and great features like pooling. The HttpClient should be used when fine grained control over the HTTP requests/response is necessary.

« More »

Classes, interfaces and traits

ErrorConverter

Converts a @see \io\vertx\jphp\ext\web\client\predicate\ResponsePredicateResult to a <code>Throwable</code> describing the error.

« More »

ResponsePredicate

A predicate on .

By default, a Vert.x Web Client request ends with an error only if something wrong happens at the network level. In other words, a 404 Not Found response, or a response with the wrong content type, are NOT considered as failures.

« More »

ResponsePredicateResult

Represents the outcome of a @see \io\vertx\jphp\ext\web\client\predicate\ResponsePredicate applied to an .

« More »

Classes, interfaces and traits

BodyCodec

A codec for encoding and decoding HTTP bodies.

« More »

Classes, interfaces and traits

WebEnvironment

Utility API to verify which environment is the web application running.

The utility will check initially for the existence of a system property under the name vertx.mode, if there is no such property then it will look under the environment variables under the name VERTX_MODE.

This value will be then used when the API is invoked. By itself this utility will not affect the behavior of your application, however you can use it to simplify your handlers, e.g.:

When the development mode is active you can log more information or disable caches.

« More »

Classes, interfaces and traits

TemplateEngine

A template template uses a specific template and the data in a routing context to render a resource into a buffer.

Concrete implementations exist for several well-known template engines.

« More »

Classes, interfaces and traits

AuthHandler

Base interface for auth handlers.

An auth handler allows your application to provide authentication/authorization support.

Auth handler requires a @see \io\vertx\jphp\ext\web\handler\SessionHandler to be on the routing chain before it.

« More »

BasicAuthHandler

An auth handler that provides HTTP Basic Authentication support.

« More »

BodyHandler

A handler which gathers the entire request body and sets it on the .

It also handles HTTP file uploads and can be used to limit body sizes.

« More »

ChainAuthHandler

An auth handler that chains to a sequence of handlers.

« More »

CookieHandler

A handler which decodes cookies from the request, makes them available in the and writes them back in the response.

« More »

CorsHandler

A handler which implements server side http://www.w3.org/TR/cors/[CORS] support for Vert.x-Web.

« More »

CSRFHandler

This handler adds a CSRF token to requests which mutate state. In order change the state a (XSRF-TOKEN) cookie is set with a unique token, that is expected to be sent back in a (X-XSRF-TOKEN) header.

The behavior is to check the request body header and cookie for validity.

This Handler requires session support, thus should be added somewhere below Session and Body handlers.

« More »

DigestAuthHandler

An auth handler that provides HTTP Basic Authentication support.

« More »

ErrorHandler

A pretty error handler for rendering error pages. When working in development mode exception details will be returned in the server responses, otherwise or when manually specified no exception details are returned in the HTTP response.

The reason the display of the exception details is by default dependent of the mode is to follow the security best practices: https://www.owasp.org/index.php/Improper_Error_Handling

« More »

FaviconHandler

A handler that serves favicons.

If no file system path is specified it will attempt to serve a resource called `favicon.ico` from the classpath.

« More »

FormLoginHandler

Handler that handles login from a form on a custom login page.

Used in conjunction with the @see \io\vertx\jphp\ext\web\handler\RedirectAuthHandler.

« More »

JWTAuthHandler

An auth handler that provides JWT Authentication support.

« More »

LoggerHandler

A handler which logs request information to the Vert.x logger.

You should mount this handler before any handler that could fail the routing context

« More »

MethodOverrideHandler

« More »

OAuth2AuthHandler

An auth handler that provides OAuth2 Authentication support. This handler is suitable for AuthCode flows.

« More »

RedirectAuthHandler

An auth handler that's used to handle auth by redirecting user to a custom login page.

« More »

ResponseContentTypeHandler

A handler which sets the response content type automatically according to the best <code>Accept</code> header match.

The header is set only if:

  • no object is stored in the routing context under the name @see \io\vertx\jphp\ext\web\handler\ResponseContentTypeHandler
  • a match is found
  • the header is not present already
  • content length header is absent or set to something different than zero
« More »

ResponseTimeHandler

Handler which adds a header `x-response-time` in the response of matching requests containing the time taken in ms to process the request.

« More »

SessionHandler

A handler that maintains a @see \io\vertx\jphp\ext\web\Session for each browser session.

It looks up the session for each request based on a session cookie which contains a session ID. It stores the session when the response is ended in the session store.

The session is available on the routing context with .

The session handler requires a @see \io\vertx\jphp\ext\web\handler\CookieHandler to be on the routing chain before it.

« More »

StaticHandler

A handler for serving static resources from the file system or classpath.

« More »

TemplateHandler

A handler which renders responses using a template engine and where the template name is selected from the URI path.

« More »

TimeoutHandler

Handler that will timeout requests if the response has not been written after a certain time.

Timeout requests will be ended with an HTTP status code 503.

« More »

UserSessionHandler

This handler should be used if you want to store the User object in the Session so it's available between different requests, without you having re-authenticate each time.

It requires that the session handler is already present on previous matching routes.

It requires an Auth provider so, if the user is deserialized from a clustered session it knows which Auth provider to associate the session with.

« More »

VirtualHostHandler

Handler that will filter requests based on the request Host name.

« More »

Classes, interfaces and traits

GraphQLHandler

A @see \io\vertx\jphp\ext\web\Route handler for GraphQL requests.

« More »

Classes, interfaces and traits

BridgeEvent

Represents an event that occurs on the event bus bridge.

Please consult the documentation for a full explanation.

« More »

SockJSHandler

A handler that allows you to handle SockJS connections from clients.

We currently support version 0.3.3 of the SockJS protocol, which can be found in this tag:

« More »

SockJSSocket

You interact with SockJS clients through instances of SockJS socket.

The API is very similar to @see \io\vertx\jphp\core\http\WebSocket. It implements both and so it can be used with

« More »

Classes, interfaces and traits

FormDataPart

A form data part of a @see \io\vertx\jphp\ext\web\multipart\MultipartForm.

« More »

MultipartForm

A multipart form.

« More »

Classes, interfaces and traits

ClusteredSessionStore

A session store which stores sessions in a distributed map so they are available across the cluster.

« More »

LocalSessionStore

A session store which is only available on a single node.

Can be used when sticky sessions are being used.

« More »

SessionStore

A session store is used to store sessions for an Vert.x-Web web app

« More »

Classes, interfaces and traits

FreeMarkerTemplateEngine

A template engine that uses the FreeMarker library.

« More »

Classes, interfaces and traits

HandlebarsTemplateEngine

A template engine that uses the Handlebars library.

« More »

Classes, interfaces and traits

JadeTemplateEngine

A template engine that uses Jade.

« More »

Classes, interfaces and traits

MVELTemplateEngine

A template engine that uses the Handlebars library.

« More »

Classes, interfaces and traits

PebbleTemplateEngine

A template engine that uses the Pebble library.

« More »

Classes, interfaces and traits

RockerTemplateEngine

A template engine that uses the Rocker library.

« More »

Classes, interfaces and traits

ThymeleafTemplateEngine

A template engine that uses the Thymeleaf library.

« More »