debugmiller

I should also add that I'm happy to port over https://github.com/requests/requests/pull/3563 but I'm unclear on why it was reverted or if the approach applies to requests 2.x

I have realized it wasn't reverted, I misread the PR that I thought reverted it.

btw, episode 3 looks like its still hanging around on twitch, just the link that is broken.

Would love to see this merged in!

If we want to allow for querying of parent paths, hashing may not work. In your example consider a query for path `b`. It should return values for both `b.c`...

> So, when user requests json.a.b.c we will return only data from path a.b.c not including data from a.b.c.d and etc. It would be nice to not have special syntax...

The syntax is less important, what I am trying to say is that I think the case of querying for a parent and also retrieving the children should not be...

For my use case this will be less helpful but I can understand that it is a development trade off you are making and this is all experimental anyways :)

> Reading all children paths for requested path will require fullscan of all the data in worst case If you store the paths sorted, you only need to binary search...

Our binaries have bloated to more than 100 MB in size because of this issue. It would be great to fix.