These are chat archives for orbitjs/orbit.js
@dgeb if we assume queries are always executed against the in-memory source (which they need to be if they're to return the combined existing and retrieved results) then I think we're looking at two different apis.
1) A query interface - the existing api on the store, returns filtered results from the memory source
2) A request for data - e.g. fetching data from a remote source
I believe (1) already provides the correct interface, we simply need to acknowledge that it only exists on the Store api. Regarding (2) it seems that you could still use a query to request the information but the results would be returned as transforms(rather than being transmitted along a permanent connector). This is different to the existing connector based setup, where the connectors are permanent. With a query based api they would only exist for the lifetime of the query/live-query.
I've tried to illustrate this a little more concretely in code at https://gist.github.com/opsb/556a3968d8f98b92d5aa.