2
0

HISTORY 3.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061
  1. For a release-by-release change history, see
  2. <http://xmlrpc-c.sourceforge.net/change.html>.
  3. XML-RPC For C/C++ was created by Eric Kidd in 2000, when XML-RPC was
  4. new and vital. Its development was funded in significant part by
  5. First Peer, Inc. Eric released the package in January 2001 and set up
  6. an extensive project to maintain it. The project used virtually every
  7. feature on Sourceforge, had about 8 official developers, and
  8. distributed code in various formats. There were mailing lists,
  9. trackers, CVS branches, RPMs, and a full PHP-based web site, just to
  10. name a few features of the project.
  11. Then everything ground to a halt in June 2001, with the disappearance
  12. of Eric. We don't know what happened to him, but Google searches in
  13. late 2004 indicated he dropped off the face of the web at that time.
  14. While people continued to use Xmlrpc-c, and some developed fixes and
  15. enhancements and posted them to the Sourceforge trackers, the release
  16. remained frozen at 0.9.10. The web site also became frozen in time.
  17. In the years that followed the great freeze, XML-RPC became
  18. marginalized by more sophisticated alternatives such as SOAP. XML-RPC
  19. consequently became rather stable and interest in Xmlrpc-c levelled
  20. off.
  21. This dark age of Xmlrpc-c lasted until October 2004, when Bryan Henderson
  22. set out to find an RPC mechanism to use in one of his projects. Bryan
  23. found XML-RPC and then Xmlrpc-c. He decided that the two were almost right
  24. for his needs, but he needed some small extensions.
  25. On finding out that the project was orphaned, Bryan decided to take it
  26. over. Bryan became the Sourceforge project administrator through
  27. Sourceforge's abandonned project process, then gathered the patches
  28. that had been submitted over the years and made a come-back release
  29. called 1.0.
  30. Bryan then proceeded to add a lot of features in subsequent releases
  31. about every two months. Most of it was code Bryan wrote himself, but
  32. significant parts were contributed by others, as you can see in the
  33. detailed history below. Among the larger enhancements was a new
  34. C++ interface; the old one was a fairly weak wrapper around the
  35. C interface and required the user to manage memory and access the
  36. underlying C structures; the new one used pure C++ principles with
  37. automatic memory management.
  38. Bryan also wrote a complete user's manual. Surprisingly, in spite of
  39. the wide array of features the project had, documentation wasn't one
  40. of them. There was only a smattering of information available on how
  41. to use the package.
  42. One significant change Bryan made to the project was to strip it down
  43. considerably. In order to concentrate the small amount of time Bryan
  44. had available for Xmlrpc-c development on actual code and
  45. documentation, Bryan had to greatly reduce the amount of bureaucracy
  46. involved in administering the project and making releases, and reduce
  47. the set of skills required to do it. Bryan made static make files
  48. (for GNU Make) to replace the two extra build stages that originally
  49. generated make files. Bryan moved away from Libtool and toward simple
  50. compiling and linking. Bryan eliminated all pre-built distributions;
  51. each of his releases consisted of a single source code tarball, and
  52. that tarball was not signed. Bryan removed some redundant sources of
  53. information from the package and the web site.