SampleSampleA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
cap-websockets
WebSocket push from a CAP service.
Facts
Last push
Where it sits
Who is behind it
Gregor WolfGregor WolfMaintains this
In the atlas: maintains 17, contributes to 59, wrote 2@gregorwolfmaintainer
In the atlas: maintains 17, contributes to 59, wrote 2@gregorwolfmaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
As a sample
- Form
- does not say
Connections
Group by
NodeRelationBasis
Functional
WebSocketWebSocketPushing updates to a browser that already has the page openCommunity only
demonstrates
authored
demonstrates WebSocket
Pushing updates to a browser that already has the page open
Download
Architecture
as mta.yaml states it at 8737541, readDownload
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
SAP HTML5 Application Repository service for SAP BTPStores built UI5 and HTML5 applications and serves them at runtime through the approuter, so an app ships no static server of its own.sap official, btp
SAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp
cap-websockets-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- cap-websockets-app-contentSAP HTML5 Application Repository service for SAP BTP
- cap-websockets-destination-contentSAP Authorization and Trust Management service, SAP HTML5 Application Repository service for SAP BTP, SAP Destination service
Documented, with no instance in the document
- @sap/xssec requires Cloud Identity Servicescap-websockets-srv
README
quoted from gregorwolf/cap-websockets, readgregorwolf/cap-websockets/README.mdthe maintainer’s wordsOn GitHub
CAP WebSockets Demo
It contains these folders and files, following the recommended project layout:
| File or Folder | Purpose |
|---|---|
app/ | content for UI frontends goes here |
db/ | your domain models and data go here |
srv/ | your service models and code go here |
package.json | project metadata and configuration |
readme.md | this getting started guide |
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaGitHub API · gregorwolf
first seen in the atlas
ecosystem and domaincap, protocols-and-apis
History in the atlas
- A sample's domain recorded what kind of thing it is, which artifact_type already says, so it sat under Learning while the capability it demonstrates sat elsewhere — filtering a domain for a worked example returned nothing. Domain now follows the single capability the sample demonstrates; a sample with no single subject stays in Learning.
- First seen.
For your agent
- Ref
artifact:gregorwolf-cap-websockets- JSON
- /artifacts/gregorwolf-cap-websockets.json
- MCP
- Connecting an agent