Roelof Naude wrote: > Peter Saint-Andre said the following on 04/02/2008 07:21 PM: >> Roelof Naude wrote: >>> hi all, >>> >>> we are currently brainstorming about pubsub. some of the content that >>> one may provide, needs to be paid for, e.g. live share price updates. >> >> Cool, we'll finally get to use the <payment-required/> error. :) >> >>> (most providers can provide a delayed feed for a fixed fee. but why >>> settle for a delayed feed if we can get a live feed?) >>> >>> what would be the best practice to allow only paid subscribers access to >>> such content? >> >> In general I think you would associate someone's JabberID with your >> database of paying customers. If someone attempts to subscribe to a >> for-pay node but they have not paid for access to that node, you would >> return a payment-required error. Probably you would use "leased >> subscriptions" as outlined in XEP-0060 -- e.g., a subscription lasts for >> 1 year and then you must renew. > > the leased subscription option looks great. from my understanding the > onus rest with the client to specify the leasing period? is there a way > to either: > 1. specify the leasing period per node during node creation (as an > config option?) > or > 2. have an external entity modify the leasing period per subscription?
I think #2 is preferable, but you'd probably do that via an interface between your billing system and the pubsub service, not directly over XMPP. Just keep extending the lease as the money comes in. :) Also I don't think you'd want the leases to be configured on a per-node basis, because IMHO that would be more complex than you really need. Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
