ServerSentEvent Chilkat2 PHP Reference Documentation

ServerSentEvent

Current Version: 11.7.0

Markdown version of this page for AI tools (v 11.7.0) · all AI docs

Chilkat.ServerSentEvent

Parse server-sent event text into event name, data, ID, and retry fields.

Chilkat.ServerSentEvent is a small helper class for parsing Server-Sent Events formatted text. Given a multi-line event block, it extracts the event name, data payload, id value, and retry interval into simple read-only properties. It is useful when an application receives event-stream text and needs to work with the structured event fields instead of manually parsing the raw lines.

Load event text

Use LoadEvent to parse a complete multi-line Server-Sent Event block.

Read event name

Inspect EventName to determine the event type supplied by the server, if an event: field is present.

Read event data

Use Data to obtain the event payload, such as JSON text from a streaming API or real-time service.

Track event IDs

Read LastEventId when the event includes an id: field that identifies the event or stream position.

Handle retry hints

Use Retry to read the server-provided retry interval when a retry: field is included.

Diagnostics

Check LastErrorText if event text cannot be parsed or if a parsing result is unexpected.

Relationship to Chilkat.WebSocket: ServerSentEvent does not manage a WebSocket connection or parse WebSocket frames. Instead, it can be used after Chilkat.WebSocket receives a text message whose payload is formatted as a Server-Sent Event. Read the WebSocket text frame, pass the event text to LoadEvent, then use EventName, Data, LastEventId, and Retry to process the event.
Common pattern: Receive or otherwise obtain a complete Server-Sent Event text block, call LoadEvent, then inspect EventName to route the event and Data to process the payload. Use LastEventId and Retry when the stream provides reconnection or event-position information.

Object Creation

use Chilkat2\ServerSentEvent;

try {
    $serverSentEvent = new ServerSentEvent();
    // ... use $serverSentEvent ...
} catch (\Chilkat2\Exception $e) {
    echo $e->getClass(), '::', $e->getMethod(), " failed\n";
    echo $e->getMessage(), "\n";              // the LastErrorText of the failed call
}
public function __construct(array $properties = [])

Creates the object. The optional array sets properties in order, as if assigned one by one (new ServerSentEvent(['VerboseLogging' => true, 'RaiseError' => false])); an unknown or read-only name throws Error. The class is defined by the chilkat2 extension (extension=chilkat2 in php.ini): there is no PHP file to include.

There is no close(): PHP frees the object when its last reference goes (unset($serverSentEvent), $serverSentEvent = null, or the end of the function or request). Objects returned by methods are independent and freed the same way. The class may be extended (class MyServerSentEvent extends \Chilkat2\ServerSentEvent); objects cannot be cloned or serialized.

public bool $RaiseError;

When true (the default), a method that fails throws Chilkat2\Exception. When false, it returns false (or null) instead, and the reason is in LastErrorText. Objects returned by a method inherit the value of the object that returned them.

Errors

Chilkat2\Exception extends RuntimeException: getMessage() is the failed call's full LastErrorText, getClass() its class ('Chilkat2\ServerSentEvent') and getMethod() the method name. The object remains usable. Methods that look something up and find nothing return null without throwing (each such method says so), methods that answer a question (HasMember, IsUnlocked, ...) return a plain bool, and property reads and writes do not throw for Chilkat reasons.

Misuse always throws, whatever RaiseError is: a wrong argument type is a TypeError (exact types under declare(strict_types=1)), a missing or extra argument an ArgumentCountError, a string containing a NUL byte or an out-of-range integer a ValueError, and an unknown property (properties are case-sensitive) or a write to a read-only one an Error. Named arguments work with the parameter names shown.

Strings are passed and returned as UTF-8; binary data is a PHP string of bytes. Unlocking: call (new \Chilkat2\GlobalSettings())->UnlockBundle('...') once at startup.

Properties

Data
public readonly string $Data;
Introduced in version 9.5.0.58

The data for the server-side event. (If the data field was empty, then this will be empty.)

top
DebugLogFilePath
public string $DebugLogFilePath;

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
EventName
public readonly string $EventName;
Introduced in version 9.5.0.58

The name of the server-side event. (If the event field was not present, then this will be empty.)

top
LastErrorHtml
public readonly string $LastErrorHtml;

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
public readonly string $LastErrorText;

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
public readonly string $LastErrorXml;

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastEventId
public readonly string $LastEventId;
Introduced in version 9.5.0.58

The content of the id field, if present.

top
LastMethodSuccess
public bool $LastMethodSuccess;

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
Retry
public readonly int $Retry;
Introduced in version 9.5.0.58

The integer value of the retry field, if it exists; otherwise, 0.

top
VerboseLogging
public bool $VerboseLogging;

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
public readonly string $Version;

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

LoadEvent
public function LoadEvent(string $eventText): bool
Introduced in version 9.5.0.58

Loads the multi-line event text into this object. For example, the $eventText for a Firebase event might look like this:

event: put
data: {"path": "/c", "data": {"foo": true, "bar": false}}

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top