-
Notifications
You must be signed in to change notification settings - Fork 309
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
separate wsgi logic from the soap parser #10
Comments
this is also needed to transform soaplib from a soap server library to a generic soap parsing library. |
the plan is to split wsgi.Application class in two. The part that will remain in wsgi module will obviously handle only the wsgi-related parts. everything else will be moved to the soaplib.Application class. it will have at least those public methods:
|
This is great. I was sitting down this morning to plan work on this issues for the rest of the week. Also, I just did a pull master and I see that you've begun implementing the plan. I'd really like to help with this but, I don't want to step on your toes. Can you let me know where you'd prefer I'd pitch in on this? I've got plenty of time to work on this right now since soaplib looks pretty core to some of our new project's. |
the interface has changed a bit, but it's essentially the same. let me stabilize the api, then we'll talk. |
i think i've got the basics to work. please hunt down bugs by writing tests / fixing the ones that fail. this is the public api. what do you think?
|
I thinks looks pretty good. I've started working on the tests today I should have a pull request for you tomorrow. |
i'm not happy with two properties of the context object:
here's how i think those issues should be addressed:
i haven't started implementing this yet. if anyone does, please drop a notice here so that we don't step on each other's toes. |
the above is implemented in 6e41a83. |
the next step is to implement alternative transports and patterns in order to validate current api and its implementation. |
zeromq transport is implemented. i consider this job accomplished. closing issue. |
in order to support transport mechanisms other than wsgi, the application logic must be separated from the wsgi logic.
The text was updated successfully, but these errors were encountered: