A side platform is a platform positioned to the side of one or more railway tracks or guideways at a railway station, tram stop, or transitway. Dual side platform stations, one for each direction of travel, is the basic station design used for double-track railway lines (as opposed to, for instance, the island platform where a single platform lies between the tracks).
A supply-side platform ( SSP) or sell-side platform is a technology platform to enable web publishers and digital out-of-home (DOOH) media owners to manage their advertising inventory, fill it with ads, and receive revenue. Many of the larger web publishers of the world use a supply-side platform to automate and optimize the selling of their ...
The definition given in this article "A side platform is a platform positioned to the side of a pair of tracks" doesn't describe some designs that are described in their own Wikipedia articles as side platforms. For example, Forest Glen station begins "Forest Glen is a side platformed Washington Metro station", even though the platforms aren't ...
A demand-side platform ( DSP) is a system that allows buyers of digital advertising inventory to manage multiple ad exchange and data exchange accounts through one interface. Real-time bidding for displaying online advertising takes place within the ad exchanges, and by utilizing a DSP, marketers can manage their bids for the banners and the ...
A two-sided market, also called a two-sided network, is an intermediary economic platform having two distinct user groups that provide each other with network benefits. The organization that creates value primarily by enabling direct interactions between two (or more) distinct types of affiliated customers is called a multi-sided platform.
Waterloo's island platform was reconfigured to be the down side platform when the station was extensively rebuilt in the late 1980s, with the unused side now facing onto a bus bay. Petone's island platform served the up main line and the suburban loop line until the suburban loop was lifted in the early 1990s.
デマンドサイドプラットフォーム (英語: Demand Side Platform, DSP ）は、デジタル広告インベントリの購入者が1つのインターフェイスを介して複数のアドエクスチェンジおよびデータエクスチェンジアカウントを管理できるようにするシステム 。
The fact that Wikipedia is built on a wiki platform (a site that can be edited by anyone at any time) has called into question the accuracy of the information it provides. For example, there are stories of celebrities and prominent political figures keeping close tabs on the Wikipedia pages detailing their careers, as critics of these ...
Bird nest. This is a blackbird nest. Once the eggs have hatched and are gone, the bird will no longer use the nest. A bird nest is a place where a bird lays its eggs. There are all kinds of nests, including cup nests, holes in the ground, and piles of twigs and leaves. The word can be used as a noun or a verb, as in – a bird nests in a nest.
- When Not to Use EventStreams
- See Also
The public EventStreams service is intended for use by small scale external tool developers. It should not be used to build production services at the WMF. WMF production services that consume events should consume directly from Kafka.
Node.js (with eventsource) Server side filtering is not supported, so if you need to filter on something like a wiki name, you'll need to do this client side, e.g.
Using sseclient. There is also a more asynchronous friendly version, here, needs Python 3.6 async generator capability. Server side filtering is not supported, so if you need to filter on something like a wiki name, you'll need to do this client side, e.g. Pywikibotsupports EventStreams with freely configurable client side filtering and automatic reconnection. Also composed streams or timestamp for historical consumption are possible. Usage sample with composed streams and timestamp:
With curl and jqSet the Acceptheader and prettify the events with jq. Setting the Accept: application/jsonwill cause EventStreams to send you newline delimited JSON objects, rather than data in the SSE format.
The list of streams that are available will change over time, so they will not be documented here. To see the active list of available streams, visit the swagger-ui documentation, or request the swagger spec directly from https://stream.wikimedia.org/?spec. The available stream URI paths all begin with /v2/stream, e.g.
SSE vs. WebSockets/Socket.IO
RCStream was written for consumption via Socket.IO, so why not continue to use it for its replacement? WebSockets doesn't use HTTP, which makes it different than most of the other services that Wikimedia runs. It is especially powerful when clients and servers need a bi-directional pipe to communicate with each other asynchronously. EventStreams only needs to send events from the server to clients, and is 100% HTTP. As such, it can be consumed using any HTTP client out there, without the need...
KafkaSSE is a library that glues a Kafka Consumer to a connected HTTP SSE client. A Kafka Consumer is assigned topics, partitions, and offsets, and then events are streamed from the consumer to the HTTP client in chunked-transfer encoding. EventStreams maps stream routes (e.g /v2/stream/recentchanges) to specific topics in Kafka.
WMF maintains several internal Kafkaclusters, producing hundreds of thousands of messages per second. It has proved to be highly scalable and feature-ful. It is multi producer and multi consumer. Our internal events are already produced through Kafka, so using it as the EventStreams backend was a natural choice. Kafka allows us to begin consuming from any message offset (that is still present on the backend Kafka cluster). This feature is what allows connected EventStreams clients to auto-res...
Server side enforced timeout
WMF's HTTP connection termination layer enforces a connection timeout of 15 minutes. A good SSE / EventSource client should be able to automatically reconnect and begin consuming at the right location using the Last-Event-ID header. See this Phabricator discussionfor more info.$wgRCFeeds: MediaWiki documentation about setting up an RCFeed. (EventStreams uses the EventBusRCEngine; EventBus.)