Hi all, I’ve found that , the api support feature is a separate part which designed to be compatible with twitter. http requests from user who’s using laconica web use another url sets, which are only useful for webbrowser client.
This design separate the service we provide into two lines, and we can naturally get the idea that same duplicate business logic must exist in these two lines. We can see some duplicate codes between them, for example(Laconica 0.8.0): twitapistatuses.php and public.php, they two invoke the same function Notice::publicStream and act similarly. Duplicate codes may cause problems when we add or modify features. Then I considered, if we can build a api support layer, who receive restful api request and return api response, we can cut down repeated work , and unify all client programs and our “official” website to be applications who base on kernel api layer. I think it is a good choice for developers who want to create a holy new commercial microblogging service using laconic, because they usually need to redesign the ui, but keep the business logic the same as they are now . What’s your opinion about that? Best regards, Ben Cao
_______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
