Stefanos Mousafeiris comments

Results 95 comments of


                                            Stefanos Mousafeiris

Socket errors when hitting the server from the browser

I can't reproduce this - is the db loaded with a lot of data? can you give the state of pg for this?

Socket errors when hitting the server from the browser

I can't reproduce either with `curl` or with `fetch` on the browser - I'm assuming given you mentioned refreshing that there's some weird race condition happening when interrupting and restarting...

Socket errors when hitting the server from the browser

We only return 304s when a request is sent with `if-none-match` and it matches the e-tag currently - assuming you're not doing that intentionally, are you pointing towards a proxy...

Don't use 409 http status code for shape invalidation

While I like the idea of `205` as a `2xx` code, it is against the spec to put a body in it and we might run into the same issues...

Create a basic mobx example

I'll pick this up

example: 100mb of analytics data in pglite

Would this be like a table/graph frontend? How would the story go other than "useShape to sync data in, the rest is all SQL/Postgres in the client"?

example: 100mb of analytics data in pglite

@KyleAMathews as previously discussed, should we morph this into a more "live streaming HackerNews data using Electric and PGlite?" rather than a plain one-time analytics workload?

example: 100mb of analytics data in pglite

Hmm if the main point is still the loading of large amounts of data then I think it's better to stick with the thing I've already been building (large fixed...

Feature request: Drop replication connection when there's no active shapes and there's not a bigger backlog of wal to process

> But wouldn't checking the WAL size periodically cause the database server to wake up anyway? I'm assuming that if this check is infrequent enough this could still work (e.g....

Only send up-to-date control header for responses with short cache timeouts

This raises a more general issue - the same chunk of the log might contain an `up-to-date` message or it might not, but it gets assigned the same `etag` and...