Re: HTTPAPI's EXAMPLExx members

[Michael Ryan <michaelrtr@xxxxxxxxx>]

   Scott -
   I like the example ideas, and I think a community forum would be
   helpful too. I've developed code to work with USPS and with Exact
   Target using HTTPAPI, and I'd be happy to share that stuff. I know a
   couple things that I had to dig for was urlencoding and the idea of
   callbacks. Maybe some examples of that?
   And thanks for all the work you do.
   - Michael

   On Thu, Jul 30, 2009 at 2:29 AM, Schmidt, Mihael
   <[1]Mihael.Schmidt@xxxxxxxxxxx> wrote:

     An example with XML-RPC would be nice to have. More or less it is
     just a
     http request with xml data and the processing of the xml response
     (much
     like soap) but that will show that you can do XML-RPC with HTTPAPI.
     I used it to access the wiki at our site. Works great.

   -----Original Message-----
   From: [2]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx

   [mailto:[3]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott
   Klement
   Sent: Wednesday, July 29, 2009 10:12 PM
   To: HTTPAPI and FTPAPI Projects

   Subject: HTTPAPI's EXAMPLExx members
   Hi folks,
   I could really use some input on what to provide for examples in
   HTTPAPI.  A lot of the current example members are outdated and no
   longer work.  Furthermore, many of them illustrate a technique that's
   rarely used.
   I would like to improve them.  Here are my thoughts:
   a) EXAMPLE1 should be the simplest possible example.
   b) Going from 1-23, they should gradually build in complexity and the
   number of features used.
   c) Examples should stick to the mainstream features, rather than
   explain
   obscure things.
   d) Examples should work out-of-the-box, possibly with small
   modifications (such as EXAMPLE2 requiring you to input your e-mail
   address) but should not require the user to find an appropriate server
   to test with.
   I think the existing EXAMPLE1 & EXAMPLE2 are okay.  And there are
   certain other EXAMPLEs that I've thought of that I know I'd like to
   provide (not necessarily in this order):
   1) EXAMPLE1 & EXAMPLE2, as-is.
   2) An example that explains how to use SSL.
   3) An example that explains how to provide user/password
   4) Example of submitting a URL-encoded form
   5) Example of submitting a multipart/form-data form
   6) Example of using XPROC to show download progress
   7) An example (current EXAMPLE15) demonstrating RSS
   8) An example of calling a RESTful web service (or two?)
   9) (currently EXAMPLE18) demonstrate SOAP (or two?)
   10) Example of using XPROC for longer soapaction
   11) An example (EXAMPLE16?) demonstrating UPS tracking
   12) Example of using strict SSL validation (current EXAMPLE22,23)
   I would appreciate some input on this stuff.  Does this make sense?
   What order should it be in?
   Specific ideas for examples would be useful, too.  Particular web
   services to call?
   Thanks in advance...
   ----------------------------------------------------------------------
   -
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   [4]http://www.scottklement.com/mailman/listinfo/ftpapi
   ----------------------------------------------------------------------
   -
   ----------------------------------------------------------------------
   -
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   [5]http://www.scottklement.com/mailman/listinfo/ftpapi
   ----------------------------------------------------------------------
   -

References

   1. mailto:Mihael.Schmidt@xxxxxxxxxxx
   2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   3. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   4. http://www.scottklement.com/mailman/listinfo/ftpapi
   5. http://www.scottklement.com/mailman/listinfo/ftpapi

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------