[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: HTTPAPI & Twitter



   Ken,
   The HTTPAPI beta can be found here:
   [1]http://www.scottklement.com/httpapi/beta/
   Brian J. Garland
   Vermont Information Processing, Inc.
   brian@xxxxxxxxxx

   From:    "Danforth, Ken" <kdanforth@xxxxxxxxxx>
   To:      "HTTPAPI and FTPAPI Projects" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
   Date:    05/25/2010 01:42 PM
   Subject: RE: HTTPAPI & Twitter
   Sent by: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     _________________________________________________________________

   Hi Scott,
   Our company is starting to use web services and we are making good use
   of HTTPAPI.  Thanks for sharing!  I'm interested in the BETA version.
    I
   don't see a link for it on your homepage.  Where can I find it?
   Ken Danforth
   Applications Architect
   Amscan, Inc.
   80 Grasslands Rd
   Elmsford, NY  10523
   Voice: 914-784-4161
   Fax: 914-784-8819
   -----Original Message-----
   From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   [[2]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott
   Klement
   Sent: Tuesday, May 25, 2010 10:05 AM
   To: HTTPAPI and FTPAPI Projects
   Subject: Re: HTTPAPI & Twitter
   hi Brian,
   If you download the current BETA version of HTTPAPI (don't bother
   trying
   the current release, you need the beta) you'll find a twitter example
   as
   member EXAMPLE10 in the HTTPAPI distribution.
   Give it a try.
   On 5/25/2010 7:22 AM, Brian@xxxxxxxxxx wrote:
   >
   >     I was toying with the idea of twitter updates directly from our
   >     applications.  I saw the Kisko offering and also Bob Cozzi's
   example
   >     using his isockets program.
   >     I figured with HTTPAPI I should be able to roll my own, but my
   lack of
   >     understanding of the process is getting to me.  I've never used
   >     HTTPAPI (big time FTPPI user) before so I know it is just my
   ignorance
   >     as to how all the pieces fit together.
   >     I only found one reference to Twitter in the archives and it was
   Scott
   >     mentioning he removed the 100-CONTINUE problem.
   >     Has anyone successfully posted updates to Twitter with HTTPAPI?
   Are
   >     you willing to share an outline, or some tips?
   >     Brian J. Garland
   >     Vermont Information Processing, Inc.
   >     brian@xxxxxxxxxx
   >
   >
   >
   >
   >
   ----------------------------------------------------------------------
   -
   > This is the FTPAPI mailing list.  To unsubscribe, please go to:
   > [3]http://www.scottklement.com/mailman/listinfo/ftpapi
   >
   ----------------------------------------------------------------------
   -
   ----------------------------------------------------------------------
   -
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   [4]http://www.scottklement.com/mailman/listinfo/ftpapi
   ----------------------------------------------------------------------
   -
   IMPORTANT NOTICE: This message is intended only for the addressee and
   may contain confidential, privileged information.
   If you are not the intended recipient, you may not use, copy or
   disclose any information contained in the message.
   If you have received this message in error, please notify the sender
   by reply e-mail and delete the message.
   ----------------------------------------------------------------------
   -
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   [5]http://www.scottklement.com/mailman/listinfo/ftpapi
   ----------------------------------------------------------------------
   -

References

   1. http://www.scottklement.com/httpapi/beta/
   2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   3. http://www.scottklement.com/mailman/listinfo/ftpapi
   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
-----------------------------------------------------------------------