Jacob Thomason

As a quick test I tried to throw the schema into a PSR16 cache, but of course that's not possible with closures. I did find this library to support closure...

@rusted-love good to know that you've already gone down this path. I guess we were thinking along the same lines - hoping for an easier solution. >Do I understand it...

For supporting multiple schemas, I was thinking we could add an additional argument, `schema`, to the following annotations: - `[Query]` - `[Mutation]` - `[Type]` - `[Input]` - `[Field]` - `[SourceField]`...

>```php >$typeMapper = $context['schemaFactory']->getRecursiveTypeMapper(); >``` So, the recursiveTypeMapper would then be responsible for determining the cached status? That means we'd have a cache hit as every type is evaluated? >```php...

@rusted-love I see what you mean now. That could work. Obviously we're talking about a lot of cache hits, but that's going to be significantly faster than recompiling these types....

>Question is about $context of webonyx, maybe you remember. Is it exposed to users anywhere? Or maybe already in use by some graphqlite internals. @rusted-love the `WebonyxGraphqlMiddleware` has the `ServerConfig::getContext`...

>>[Right]: maybe resolved in this PR https://github.com/thecodingmachine/graphqlite/pull/571 (@oprypkhantc confirm) >>[Logged]: maybe resolved in this PR https://github.com/thecodingmachine/graphqlite/pull/571 (@oprypkhantc confirm) > >Correct, these are now working properly with a shared Schema instance,...

@rusted-love this is only for executing queries “manually” using webonyx, right? Or are you talking about having to pass `Context` elsewhere? If only for “manual” or “custom” execution, I think...

Thanks for this @shish! Let's stick with APCu in the example with a code comment for Filesystem, like #662.

Let's update this PR such that the docs direct the reader to the examples, instead of maintaining any code here.