Live

Live tables use server-sent events (SSE) to automatically update your table content for any user viewing your table based on server side state.

This means you could, for example, have your user's tables almost immediately update if a model's data changes server side, without relying on polling.

TIP

Iridium also supports basic polling options for a simpler approach.

Getting Started

Live tables require server-sent events to be enabled a part of your panel.

Certain Iridium components has a FeId which stands for front-end ID. This is a globally unique identifier used to distinguish certain components on the client side.

For tables, the FeId is set for you, and is used to receive SSE requesting the table to update itself, as well as being used as a prefix for the table's filter/searching fields in the URL (mandatory if multiple tables are present on the same page).

Triggering an update request

Anywhere in your application you can call upon Iridium's sse package to issue a sse broadcast to all clients telling them that if a component with a specific FeId is on their page, they need to trigger it's update method.

Minor Security concerns

For Iridium's alpha, all registered clients will receive a broadcast notification for a FeId regardless of whether the assocaited component for the FeId is present on their page. This means even FeId on pages the client does not have access to will be broadcast to them.

This is a very minor leak of information, and won't expose much unless you name your FeId for your table something like <<Insert Joe Smith's social security number>>, but it's worth keeping in mind. We recommend creating a constant that contains a random id mapped to a more explicit name so you can reference it in your source code, without exposing any intelligible information client side.

Iridium may make this broadcasting more sophisticated post-alpha to avoid requiring all clients to receive all broadcasts. Right now it's a medium lift for minor gain.