ehahn9 kirjoitti:
> Thanks, all.  Alas, no perfect solution:
> 
> * I had read about others' attempts by extracting the token from the
> HTML (the "CURL" threads) - too hacky methinks.
> 
> * The email submission is a problem because my trac is running at a
> hoster who doesn't like redirecting aliases to executables (although
> to be fair, I haven't pressed hard on this).
> 
> * The XmlRpcPlugin looks like my best shot. Alas, that adds a fair bit
> of xml library code to the client (which is tiny today) and there is
> some commentary about the plugin not playing nice with the login plug-
> in I'm using.
> 
> Seems odd (to me) that Trac, which is so wonderful in every way
> doesn't have friendly URIs for posting.  I guess there's no good way
> to do this with CSRF support enabled. <sigh>.

Well XML-RPC (and JSON-RPC that I'm working on) does pretty nice job. If 
you don't use stardard HTTP based authentication things have tendency to 
get tricky.

I had same problem: I wanted lightweight solution to do remote requests. 
I felt that XmlRpc is a bit heavyweight solution (need complex XML 
parser etc.) so I'm now trying to get JSON-RPC working.

So if only thing you need is ticket handling I can pass my JSON part for 
that. It works, but not the final solution.

-- 

Jani Tiainen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to