Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
Opinions on a TxP API?
I am planning on creating an API plugin (drop-in the TxP folder script, actually) for TextPattern, and am unsure about what format the client-server requests should be. The three choices I am considering right now are:
The blogger API
Pros: well supported, would instantly open TxP up to most blog posting apps. de facto standard
Cons: not meant for systems as powerful as TxP. would require either not allowing most options (even as basic as a descriptive paragraph) or modifying the API, killing the main advantage
LiveJournal API
Pros: well supported with large number of available clients. Would need to be modified, but most LJ clients are OSS so client app mods would be simple (at least more so than starting from scratch)
Cons: would still require reworking of everything… feels like it would be a kludge
Custom API (XML based):
Pros: would be designed esp for TxP. XML is easily parsed so creating clients would not be too difficult. XML is also easily expandable so it could grow with TxP
Cons: reinventing the wheel, esp on client apps
Pros or cons i missed on any of these? Suggestions on which would work best? Is there a better API I left out? I plan on getting feedback before I hack anything together and am reading comments… leave some. :)
Insert witty sig file here.
Offline
Pages: 1