"Brian Beck" <[EMAIL PROTECTED]> writes: > That request part isn't what's making it hard to integrate, it's the > model. Reading the tag schema doesn't really help, either. Am I > supposed to modify tasty's Item class to be the model for the items I > want tagged? Or is it supposed to exist as a distinct table and be > linked to the models in my application? I got frustrated pretty > quickly trying to fit tasty into my app, so a 'real' client > implementation example would help a lot.
maybe you're misunderstanding. tasty is designed to run as its own service, *entirely* seperate from your application. you only access it through HTTP. it should be not just a distinct table, but a distinct database. it could exist on a seperate machine even. tasty then views items and users as just ids. so if you had, eg a blog with posts and users and user 'bob' tags post #426 with the 'toread' tag, your application would make an HTTP POST request to http://yourtastyserver.example.com/service/yourservice/user/bob/item/426/tag/toread/ then, to get a list of bob's tags on post #426 later, you would make a GET request to http://yourtastyserver.example.com/service/yourservice/user/bob/item/426/ or, to see all the tags on post #426 http://yourtastyserver.example.com/service/yourservice/item/426/ to see all of bob's tags, you request http://yourtastyserver.example.com/service/yourservice/user/bob/ what you use for item ids and user ids is up to your application. they can be any urlencoded string (well, except encoded '/'s at the moment due to a bug in the current stable version of cherrypy). -- anders pearson : http://www.columbia.edu/~anders/ C C N M T L : http://www.ccnmtl.columbia.edu/ weblog : http://thraxil.org/
pgpisCWaN7EvZ.pgp
Description: PGP signature
