4 ms·
I’m pretty sure there is a complete webdav implementation which ships with golang in the stdlib… Why do you need an external library for this? You just need to
by cyberpunk 10mo ago
I’m pretty sure there is a complete webdav implementation which ships with golang in the stdlib… Why do you need an external library for this? You just need to wrap it in a main.go and boom, webdav server.
- jerf 10mo agoIt's in the extended standard library at https://pkg.go.dev/golang.org/x/net/webdav https://pkg.go.dev/golang.org/x/net/webdav . Whether or not it would meet their needs, they'd have to tell us. I don't think they told us enough to evaluate that ourselves, and even if they did doing even a quick job is probably at least an hour's careful reading and comparing and that's past my budget for an HN post. And they're not obligated to give us an absolutely complete accounting of everything they considered. That just generates other complaints.
- packetlost 10mo agoIt's in golang.org/x/net, but yeah. I don't know if it's complete though.
- bborud 10mo agoPlease read the posting. He says why in the second paragraph.
- cyberpunk 10mo agoI did read the second paragraph: > Now before you mention NIH syndrome, yes, we looked at the existing Go implementation, go-webdav. This library was lacking some key features we needed, like server-side collection synchronization, and the interfaces didn’t really align with our data model. This is also going to be a key feature of our product, so we should have some level of ownership for what gets implemented. This is a different, non x/net library.
- candiddevmike 10mo agoAuthor here, the stdlib webdav library is less complete than the go-webdav library. > You just need to wrap it in a main.go and boom, webdav server. Lol
- deleted 10mo ago[deleted]
- cyberpunk 10mo agoOkay, webdav server good enough to feed my home media players at least ;)