Lists are observable arrays of recordnames (not their data!).
Lists and recordnames have what a computer science teacher would call an n:m-relationship - a list can contain many recordnames and a recordname can be part of many lists.
To make life easier, lists come with all sorts of convenience methods. You can add an entry at a specific index using
addEntry( recordName, index ), remove entries from anywhere within the list using
removeEntry( recordName ), set or get all entries or check if the list
Apart from that, lists are quite similar to records. They notify you
whenReady(), can be
subscribe() to and need to be
discard() after usage.
What are lists useful for?
Lists are used whenever records need to be combined into collections. Let's take the infamous TodoMVC for example. When built with deepstreamHub, each task would be a record, containing the
title and a
Each record is identified by a unique name, e.g.
todo/ part of the name identifies the category the record belongs to and specifies the table within the database it will be stored in. It does however NOT automatically add the record to a list of todos.
To organize our tasks in a list called
todos, we would need to explicitly create it using
var todos = ds.record.getList( 'todos' );
and add our recordnames as entries
todos.setEntries([ 'todo/ikfndidw-1973pnhmyk7', 'todo/ikfndiqx-43jdj23bsdf', 'todo/ikfndidt-5sdk3zag354' ]);
Taking it a step further
deepstreamHub is all about combining simple building blocks into powerful apps - and lists are no exception. Nesting references to lists within records and references to records within lists allows you to model your application's data-layer as a fully synced and observable tree structure.
Using lists with anonymous records
Lists are often used to power selection panels for anonymous records.
Why do lists not contain or subscribe to the actual record data?
Records are more than just their data. They have their own subscribe/discard lifecycle which tends to be closely associated with the component that renders them. Naturally, this component is the best place to request the record and manage its lifecycle.
Recordnames are lightweight strings that can easily be passed around, e.g. as
props to React components or as
data-model to an Android listview.
This also addresses one of the major challenges of developing realtime apps: Using bandwidth efficiently and minimizing the amount of data that's send over the wire. One of the best ways to achieve this is by limiting subscriptions to the records that are currently in view. Lists help with that by providing the necessary structure to create infinite grids or panels that automatically load and discard data while the user scrolls.
What happens if my list gets too long?
deepstreamHub uses a highly optimised protocol that keeps message sizes extremely low. This means that even lists with 1000+ entries of longer record names rarely exceed 20-30kb.