anders pearson wrote: > 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.
Ah, got'cha. It seems impractical performance-wise since there is indirection through HTTP, and it will take some extra work to write complex queries involving both tags and separate attributes. But I was actually impressed with the responsiveness on thraxil.org, so I'll give it another try until it works. Thanks for clearing that up,
