-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote, Archive or WIP #129
Comments
my opinions:
But I don't really have production apps - so I can't say that they're production ready or not |
Lgtm |
any thoughts @hugetim , @jshaffstall ? |
Non-blocking is definitely something I'd love to use in production. I haven't played with it as it currently exists, though, so can't say whether it's ready. But I do have specific situations in my production app where it'd be useful, though not critical. Kompot has the the multi-server call wrapping. I can't say I'd ever use the serialization features of it, but the server call wrapping would be a useful utility. It allows one to design server functions based on each having a single responsibility, but still execute a bunch in a single server interaction, which I think is very important for writing well designed apps. I love the idea of Atomic, so definitely want to see it continue. It's such a change in structure for apps, though, that I haven't played with it. |
I'm a big fan of Kompot, at least in theory. I haven't used it yet but expect that I would use all aspects of it as part of anvil_extras. |
So, promote non-blocking and leave atomic, kompot and web worker here as WIP? |
Sounds good to me. Might be worth pulling the server call batching out of Kompot and into a feature of its own. |
This project should only include work which we are currently investigating. For each of the modules, we need to decide whether it's:
The text was updated successfully, but these errors were encountered: