-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
Refactor Code and Docs "Server" Verbiage #720
Comments
I basically agree and was thinking about this in my last PR. Only difference is that maybe we could use "Web Application" instead of "Web Framework". Framework is a bit generic - in principle one can have frameworks for building both apps and servers. With that I'd probably rename |
"web application" is rough. Although it makes sense, that namespace is currently getting used up by Progressive Web Applications, so it ends up feeling incorrectly labeled. |
I haven't given much thought on what we could rename idom.server to. Maybe I'm currently on vacation, I'll give more thought to this next week. |
I'll likely update this list if I think of more. But this is what I have for now:
|
I'm thinking |
We should be able to use the same language as these app frameworks do in their documentation. |
In that context, app is referring to the WSGI/ASGI application. But in our case, the end user isn't really directly interfacing with the WSGI/ASGI app through IDOM. At the same time, I'm personally not a big fan of any of the options I posted. I'd think of it from a few steps back. What is it that the module currently trying to do, and what might it do in the future? From my perspective:
This module really sounds like a compatibility layer to me. |
Besides |
Actually, didn't see |
Agreed. Semantically, |
Current Situation
There are a lot of locations in the source & docs where we currently call things "server", when they really should be called "web frameworks"
Proposed Actions
Rename functions, comments, and docs while keeping these guidelines in mind
The text was updated successfully, but these errors were encountered: