With the XMLRPC interface in place and conveniently accessibly through
the normal web interface, not much is missing to allow client
applications to interact with Roundup directly.

This patch encapsulates the XMLRPC communication, and allows clients to
access a Roundup tracker through a simple and pythonic API.

How does this look ? I propose to put that into the Roundup source tree,
and package it separately for binary packages, so users can install it
independently from the server-side code.

How does this sound ?

As I just checked in a change that adds a 'schema()' method to the
XMLRPC interface, here is a new version of the client-side library that
mirrors that addition.

Any suggestion where to put this file in the source tree ? We will also
want to think about how to package it, as it can be installed
stand-alone, without the server-side code.

Richard, do you have any opinion on this ? Any idea how this would be
packaged ? Some users may only want to install the client-side...

Thanks,

Gee, it's small isn't it :)

It'd be a bit much to ask users of this library to install roundup itself.

I actually think it might be an idea to create a new dist for this, so it should belong in a 
separate tree of the SVN. Perhaps /roundup-client/?

Stefan,
I would like to get this into the tree.

Maybe under share/roundup/xml_client_library or
roundup/client_lib/xml_rpc so it will get installed on the
roundup server and people can copy the file to the client
system as needed.

However I would like to include an example or two of how to use it.
Do you have an example using the classic demo tracker?

Ping Stefan:

This needs updating to python3 and I still need doc/example of use.

Do you have some time to bring this up to date and document it?

-- rouilj

Do you have a publicly accessible tracker instance I could use to test this ?
I'm afraid I don't know how to set up a new instance, and I don't have time right now to dive in to learn it.
Thanks,

Hi Stefan:

In message <1615674083.93.0.00855263044248.issue2550554@roundup.psfhosted.org>,
Stefan Seefeld writes:
>Do you have a publicly accessible tracker instance I could use to
>test this ? I'm afraid I don't know how to set up a new instance,
>and I don't have time right now to dive in to learn it.

Try:

   https://rouilj.dynamic-dns dot net/demo/

replacing "dot" with a '.'. The xmlrpc endpoint should be;

   https://rouilj.dynamic-dns dot net/demo/xmlrpc

Login user: demo, password: demo.

That user should have the /xmlrpc endpoint enabled. If you go the the
tracker and look at issue1, you will have directions on the various
logins.

Note this is an extensively modified tracker compared to the classic
tracker, but the issue object has messages, title, status etc. so you
should be able to generate an example that will work with the classic
tracker.

Thanks for taking a shot at creating an example.

Hi Stefan:

I forgot to mention that I have anti-csrf methods enabled.
So you need to add the following headers to your request:

"Referer", "https://rouilj.dynamic-dns dot net/demo/
"Origin", "https://rouilj.dynamic-dns dot net
"X-Requested-With": "xmlrpc"

See the documentation in the doc/xmlrpc.txt for an more detailed
example.

				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.

Hi Stefan:

Is there anything more you need from me?

-- rouilj

Hi Stefan:

Just pinging you to see if you need anything from me.

-- rouilj

I tried a bit but couldn't get it to work with your server as end-point.

But to be honest, I'm also not sure this is worth the trouble: It has been a very long time since I last worked with and contributed to Roundup, so getting back into Roundup's code requires quite a bit of work for me now.
I can't believe that it's hard to rewrite my original patch to work with a more recent version of the `xmlrpc` API. So if there is real interest, I'm sure someone with a current interest into the project will be able to fill in the missing bits.

Hi Stefan:

> I tried a bit but couldn't get it to work with your server as end-
point.

That's too bad.

> But to be honest, I'm also not sure this is worth the trouble:

Fair enough. Everything has its time nd this has been hanging around
for a while.

I'll close it and mark it as later in case somebody wants to
pick it up.

Have a great week.

-- rouilj