Call for Community Testing: 3.9.5 C WS Core

What is a "Call for Community Testing"?

A Call for Community Testing is a mechanism to notify our users that new Globus code is available for testing in the field. Through these calls, the Globus Alliance hopes to expose its code to a wide variety of usage scenarios early in its development process. The ultimate goals are to catch bugs that have historically been found only after final releases, and to elicit feedback from the community on ways our software can be improved.

Participating in the C WS Core Testing Call is easy!

  1. Optional: Consider sending mail to testing@globus.org to let us know that you're helping out and describing what you intend to test.
  2. Install the software in a non-production environment. Use the 3.9.5 distribution from http://www-unix.globus.org/toolkit/downloads/development/; the code can also be retrieved directly from CVS using the tag [tag].
  3. Exercise the software.
  4. Log your experiences in http://bugzilla.globus.org/globus/ under the "WS Core" product ("globus_wsrf_core" component). Please mention 3.9.5 explicitly in the body of the report.
  5. Optional: Consider sending descriptions of your tests to testing@globus.org so that we might use them to build standard tests in the future.
  6. If you have any questions or comments about the process, send an email to testing@globus.org.
  7. If you have any questions or comments regarding this component, join the gt4-friends list to participate in discussions with other testers. (To subscribe, send an email to majordomo@globus.org containing the words "subscribe gt4-friends" in the message body.)

Testing period

The testing period for this call is December 17 - January 31 2005.

About C WS Core

The C WS Core provides a basic toolset in C for creating WSRF-enabled web services and clients conforming to the WS-Resource and WS-Notification specifications.

Reasons for testing C WS Core

  • We need volunteers to exercise C WS Core to discover performance and scalability problems. Since C WS Core is a critical piece to any service built on top of it, its performance and scalability directly affects the service. Therefore, improving the C WS Core performance most likely will improve the service performance.
  • We need volunteers for C WS Core to discover functionality and usability problems. Improving usability and functionality will make the software easier to use and develop.

Technology dependencies

C WS Core depends on the following GT components:

  • C Common Libraries
  • Pre-WS Authentication and Authorization (GSI)
  • Globus XIO (used by C WS core for efficient HTTP and TCP transport)

C WS Core depends on the following 3rd party software:

  • Libxml2 (used by C WS Core for SOAP XML parsing and WSDL parsing)
  • OpenSSL (used by C WS Core for Security)
  • JavaScript (used by C WS Core as a template language to generate the C bindings from WSDL schemas)

Environment/build parameters and other special conditions to test

  1. Testing on a platform that is not listed in tested platforms.
  2. Stability tests: making thousands of requests to the container for a long period of time without restarting the container
  3. Concurrency tests: making hundreds of concurrent requests to the container