You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a customer that needs cookie support in his FOSS WebDAV-client. It is a long stack and on the bottom is neon. I wonder on what layer I should implement that on.
neon has a history of adding and removing cookie support. I feel cookie support is orthogonal to WebDAV and should be implemented elsewhere, but if cookie-support is in demand in neon, I would implement it here. Please let me know if you're interested.
The text was updated successfully, but these errors were encountered:
I had a very half-baked implementation at one point which I removed since it was pretty poor. I guess I'm not totally against it. Do you have an idea of the API which could be exposed, and any rough guess what size of implementation it is?
Thanks a lot for your answer. I have nothing concrete, yet. We will implement a quick solution that solves the customers problem in the layer [1] using neon. The next step in our project is to plan and maybe prototype an upstreamable version. Your answer means that we will consider implementing in neon. Which would benefit the community most, but also means that the solution has to more generic. I'll open an issue with a proposal once the project reached that stage.
I have a customer that needs cookie support in his FOSS WebDAV-client. It is a long stack and on the bottom is neon. I wonder on what layer I should implement that on.
neon has a history of adding and removing cookie support. I feel cookie support is orthogonal to WebDAV and should be implemented elsewhere, but if cookie-support is in demand in neon, I would implement it here. Please let me know if you're interested.
The text was updated successfully, but these errors were encountered: