changed:
-
To Mr. Evans:

I'm not sure exactly how we're supposed to respond to direct
questions; hopefully this note is noticed.

My original plan was to initially implement a simple wrapper class
on top of a urllib2 scraper in order to access the Tracker; this
would provide the necessary functionality (providing a library for
additional client-side access) with a minimum of changes necessary
on the server.

After proposing this idea to the Roundup development community, the
existing developers felt that scraping wasn't the best solution.
While it will work for out-of-the-box Trackers, it will likely begin
to fail on highly modified Trackers (those with new fields, for
instance, or entirely new classes).

Given that I plan to make the transport layer as transparent as
possible to the library, I see no reason why an urllib2 transport
couldn't be added after the fact.  Indeed, I think this would have
certain advantages; namely, it would work on older, unmodified
versions of Roundup.  I may add an urllib2 transport once the SoC
project is complete.

More information on the developer's conversation can be found in
the mailing list archive:
http://sourceforge.net/mailarchive/forum.php?thread_id=10285465&forum_id=1100


Timothy J. Warren