What I really really want is a tool exactly like that, but one that can operate via HTTP, remotely.
Ultimately the real API is the HTTP API. Assuming SQLite (or any SQL) immediately makes it less useful for more advanced users. A standard tool might also open the door to allowing the tool to be useful for non-sabredav systems (if we make a great standard API specification). That said, the tool as it is today might still be useful for some people. Maybe you can just open source it? We can post it from our twitter and put it on the sabre.io blog too. On Monday, January 16, 2017 at 11:39:58 AM UTC-5, stev...@niteflyte.net wrote: > > > > On Sunday, January 15, 2017 at 9:25:07 PM UTC-8, Evert Pot wrote: >> >> Unfortunately there isn't one yet. Everything else has an API because it >> also has a way for DAV clients to manipulate. Since there's no real DAV >> standard for managing users, I've also never built an API. >> > > I can contribute mine if you like... you'll have to "Sabre-ize" it; fix > all the mistakes; and remove all the assumptions (like I assumed SQLite, > always) :-) > > My code is designed to be used in a command-line interface as well so > there's lots of error-checking with corresponding text messages. I use > Respect\Validation to do most of that stuff (very handy). All tolled, > everything is about 350K. > > -- sw > > -- You received this message because you are subscribed to the Google Groups "SabreDAV Discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to sabredav-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sabredav-discuss/7d45da2a-84cb-4786-89b0-e0ed7ba0dd5c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
