Download the PHP package ikarus/sps without Composer
On this page you can find all versions of the php package ikarus/sps. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 sps
Ikarus SPS
Ikarus SPS is an attempt to run PHP on a device as independent SPS.
Installation
This reporitory is a package that can be intalled using composer: `
How Ikarus SPS works
The Ikarus SPS engine distinguish between two kinds of run modes:
- Cycle based engine
This engine type defines a fixed frequency, for example 2Hz, which means, that the engine updates twice per second. - Event based engine
The event based engine waits until an event gets triggered from one of its plugins.
So it depends of your requirements, which kind of SPS engine you prefer.
General workflow
- There is usually one instance of a SPS Engine running on a device.
- Eventbased: This instance needs two kinds of plugins: listeners and triggers.
or cyclebased: The instance needs only cycle plugins. - The listener waits until something happens in the SPS to perform an action. (SPS to device)
Example: A timer event was triggered and the listener now instructs a motor to close the door. - A trigger wait until something happens on the device and informs the SPS. (Device to SPS)
Example: An input sensor notifies that the door is closed or a timer triggers that time is up. - Run the engine, now the plugins get active and the SPS runs.
Multiprocessing
PHP has an extension that allows forking a process.
This feature is used to multitask the SPS Engine.
All trigger plugins are dispatched to a separate process. Now they can wait for an event of the device, while the SPS Engine and its listeners continue working.
SPS Trigger Plugins
As described above, trigger plugins run in a separate process to avoid that the SPS Engine gets blocked because of a listener (Example: listening on a socket blocks the thread until something is available to read from the socket.)
But this has one disadvantage:
- An SPS trigger does not share the same memory as the SPS Engine and its listeners.
This means:
- An SPS trigger gets a copy of the environment at engine start.
After that, everything it does (reading object properties, defining variables, etc) does not affect the SPS Engine anymore (and vice versa!)
To solve this problem, the Ikarus SPS package has dispatchable events that can be transmitted from and to SPS triggers.
All versions of sps with dependencies
tasoft/event-manager Version ^1.0
tasoft/process Version ^1.0
tasoft/value-injector Version ^1.0
ext-sockets Version *
ext-pcntl Version *
ext-posix Version *