The issue, to my mind, is about alternatives.  The RPG shops already using YAJL or whatever are happy and have no real reason to change.

However, the many good, long-time RPG shops that find that they must move into the XML/JSON world can get there with existing people a lot quicker with IWS.  IWS provides existing teams with an on-ramp that is gradual, productive, and effective from about Day 4 (with a decent tutorial/teacher).


On 7/18/2019 1:17 PM, Jim Oberholtzer wrote:
My thought was the client and server program both “speak” JSON between them
and IWS manages the server instance etc. That’s where Scott Klement’s YAJL
and HTTPapi come into play.

Am I wrong? I can see where IWS could be avoided.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.