Javier Domingo wrote: > > > Be specific. What is the problem? > > > > I hope that this will be answered, so that everyone can understand > > the concrete issues. > > I forgot to answer ^^!, the problem is that if I want to reimplement > my own ticketing system, using the existing one as a base
But that wasn't what I suggested.. I suggested to implement dynamic permissions while staying with the existing ticketing system unchanged for ticket contents. The only code you would need to write is for permission decisions, the result of your code within a request would be one or more permissions set, and the regular permissions system allows or disallows access based on that. Of course you would still need to do database things in order to make those permission decisions, but aren't there also some things in Trac to help with that? In the end, if you keep your SQL simple enough it just works<tm> everywhere. //Peter -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
