Re: HTTP API - two step communications.

[Henrik Rützou <hr@xxxxxxxxxxxx>]

   Scott,

   �
   No, I don't suggest making a HTTPAPI specific JSON parser and you
   already have�
   the JSON Utilities by Mihael Schmidt - your way.

   But JSON is the "next" format we in general has to be "ready for", not
   that I'm not,

   as I demonstrated in this tread - but as you know - "I do it my way"
   that is only

   one way.

   On Wed, Oct 12, 2011 at 12:18 AM, Scott Klement
   <[1]sk@xxxxxxxxxxxxxxxx> wrote:

     Henrik,
     I agree completely.
     Does your message carry any hidden meaning...? �(Such as a
     suggestion
     that a JSON parser be added to HTTPAPI?)

   On 10/11/2011 3:04 PM, Henrik Rützou wrote:
   >
   > � � many online services returns JSON today, just take all the
   Google
   > � � API's ... and when
   >
   > � � using SOA in a MCA/MCD you must expect many more services to
   answer in
   > � � JSON.

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

   --

   Regards,

   Henrik Rützou

   �
   [3]http://powerEXT.com

   �
   [plogofull200.png]

References

   1. mailto:sk@xxxxxxxxxxxxxxxx
   2. http://www.scottklement.com/mailman/listinfo/ftpapi
   3. http://powerext.com/

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