Some questions to start using it about websub-server HOT 3 CLOSED

1. See AddHandler and events.go - you can add funcs which take these as the only argument and they'll be passed when something happens, meaning you can log anything you'd like. There's also the Validator which can verify it's a topic you handle.
2. Yes, see the store package. This is made specifically to allow something like MySQL, SQLite, etc to store records. Note that these aren't implemented by default as sqlite, at least, would require cgo to build and complicating the package more. Third party packages would be greatly appreciated for implementations of these.
3. Yep! They must validate with the hub.challenge, See this code which handles verification of challenges against the endpoint. The subscriptions are not stored until verified.
4. The publishing spec is weird in general, but requires hub.topic to specify which topic it's updating. The ContentProvider type provides a way for the hub to retrieve content if you had something custom, or simply pass through data if you'd like it to. The default is to send an HTTP GET request to the topic url.
5. I'll look into this, seems to be a bug with the lease time. I added an override to the DecodeHook for strings, seems like I didn't add one for integers.

from websub-server.

@pierrocknroll

I've created a basic, albeit untested sql store. I'll likely test it this weekend, but figured I'd push it up into the feature/mysql branch for now!

Edit: Tested (basic) sql store added to the main branch under store/database!

from websub-server.

Thanks a lot, it's clear for me now :) 👍

from websub-server.