Adam Jones wrote: > What do you plan on doing with that data? The only big problem (from > TG's perspective) with using SA at the moment is that it does not have > the same level of integration that SO does. So things like Identity, > Fastdata, and anything else that depends on integration with the ORM > will be a little more difficult. If all you need from that data is to > access it you have just about all of the support for SA that you need.
I definitly need Identity. I've already implemented an identity provider which fits my needs, but it's based on SO, as I took sosmbprovider as a starting point (and I didn't have any TG experience before). It would not be that hard to switch it to use SA, but I don't want to switch as long as there are too many issues with SA and other TG components. And I do want to be able to use all TG features. > That said SA is still relatively new, and I would not be suprised if > another breaking api change happens. TG has many nice features, but currently it seems to be a little bit stressful keeping an TG-powered application up-to-date. It seems that some components (e. g. SA) are just too new. Hmm... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
