Integrate xmlrpc-streaming gem
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 41
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
There is a very old gem on https://github.com/washu/xmlrpc-streaming, with the following feature set:
- Base64 now accepts an IO object to its constructor
- The XMLRPC request will now be streamed to the server. This will be a little faster and generate much less garbage. It should also fix issues where large Base64 objects sent to the server can cause out of memory errors
- Base64 now has a to_io methods that will give access to the underlying data as a IO object note: this is the raw data.
- set_writer will be ignored if this module has been loaded.
- the parser will now try the following, nokogiri, libxml and finally fallback to REXML
- This module can be used completely transparently, just require the lib and nothing else needs done
The current release of this Gem is 0.1.0, and it hasn't been updated since 2011. The xmlrpc gem has a parser using libxml nowadays, but these two differ. I have no idea of the gem still works with the current release of xmlrpc.
It would be nice to have the functionality in the addon merged into the base release. I'm open to making the changes, but first I want to be sure this would be accepted, and that merging this foreign gem is even allowed (notify for @washu)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the xmlrpc-streaming gem's listed features with the current xmlrpc parser using libxml and request handling. Confirm whether the old gem still works with the current xmlrpc release and whether maintainers accept integrating it; done means an agreed implementation scope and compatibility plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100