Download the PHP package evertharmeling/sparkcore without Composer
On this page you can find all versions of the php package evertharmeling/sparkcore. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download evertharmeling/sparkcore
More information about evertharmeling/sparkcore
Files in evertharmeling/sparkcore
Package sparkcore
Short Description PHP classes who help interacting with the sparkcore. For example consume Server Side Events.
License MIT
Homepage https://github.com/evertharmeling/sparkcore
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package sparkcore
sparkcore
PHP classes who help interacting with the sparkcore. For example consume Server Side Events.
Implementation
First create your own Sparkhose class which extends SparkCore\Stream\Sparkhose.
This library is implemented as an abstract class (Sparkhose) that is extended to utilize the SparkCore event stream.
This design choice was made to allow the utilization of the library with the minimal amount of code to be written, whilst keeping things in a PHP/OO-style way (ie: no callbacks, etc).
In its most simple form, you need to extended the class and implement an enqueueEvent() method:
Now your able to initiate your own Sparkhose class:
Specific Event
Optionally you can listen to a specific event by setting the 'event_name' on the Sparkhose object.
Logging
By passing a Logger (Psr/Log) instance to the Sparkhose object, you'll be able to see logging.
Please note that this library is only intended to work in a CLI environment (not embedded in a web-script and run by your webserver) and will likely require some form of multi-processing (either pcntl_fork() or entirely separate processes and some knowledge of how multi-processing works on your and your hosting providers operating systems). See below for more details.
Collecting and Processing
An important concept to understand is the separation of collection and processing functionality.
To prevent latency problems and plan for scale, design your client with decoupled collection, processing and persistence components. The collection component should efficiently handle connecting to the Streaming API and retrieving responses, as well as reconnecting in the event of network failure, and hand-off statuses via an asynchronous queueing mechanism to application specific processing and persistence components. This component should be isolated from any subsequent downstream processing backlog or maintenance, otherwise queuing will occur in the Streaming API. Eventually your client will be disconnected, resulting in data loss.
For example, consume statuses from your queue or store of choice, parse them, extract the fields relevant to your application, etc. It is because of this recommendation that the only (required) method that need be implemented is enqueueStatus(). It is up to you to decide how you want to manage queueing of your raw statuses, but it is important that you just queue them and don't try to do full processing inline as this could cause your client to lag and get disconnected or (probably eventually) banned.
