Merged
Conversation
mkucharz
requested changes
Oct 25, 2018
| - **Users Management (users)** - service to store and manage users and groups of your application | ||
| - **Event Loop (events)** - service to emit events which can be caught by any Socket | ||
| - **Realtime Channels (channels)** - implement publish/subscribe model for realtime communication | ||
| - **Response method (response)** - lets you send response from Socket |
Member
There was a problem hiding this comment.
Those are not actually CORE services, those are just helpers to use inside a Socket. Lets make here two lists (note changes in description also):
Something like that:
Syncano provides various Core Services and Core library contains an interface to them:
- Database (data) - NoSQL database to store your application data
- Users Management (users) - service to store and manage users and groups of your application
- Event Loop (events) - service to emit events which can be caught by any Socket
- Realtime Channels (channels) - implement publish/subscribe model for realtime communication
Library also contains number of helpers for working with a scripts:
- Response method (response) - lets you send custom response from the script
- Logging (logger) - logger which helps with debugging scripts and measuring time of execution
Contributor
Author
There was a problem hiding this comment.
Proposed changes are in new commit, something like that you had in mind?
mkucharz
requested changes
Oct 25, 2018
mkucharz
requested changes
Oct 25, 2018
mattlsp
reviewed
Oct 26, 2018
|
|
||
| The Core API library should be used in the **Syncano Sockets** (inside the scripts powering the Syncano Sockets) to communicate with the **Syncano Core Services** and 3rd party integrated platforms. Syncano provides various Core Services: | ||
| - **Database (db)** - NoSQL database to store your application data | ||
| Syncano provides various Core Services and Core library contains an interface to intereact with them: |
mattlsp
reviewed
Oct 26, 2018
| }) | ||
| ``` | ||
|
|
||
| Catch `events` by subscribing to a Socket emmiting an event. |
ksyhoo
commented
Oct 26, 2018
| - **Users Management (users)** - service to store and manage users and groups of your application | ||
| - **Event Loop (events)** - service to emit events which can be caught by any Socket | ||
| - **Realtime Channels (channels)** - implement publish/subscribe model for realtime communication | ||
| - **Response method (response)** - lets you send response from Socket |
Contributor
Author
There was a problem hiding this comment.
Proposed changes are in new commit, something like that you had in mind?
mattlsp
approved these changes
Oct 26, 2018
mkucharz
approved these changes
Oct 26, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.