Below are notes on changes in  the IFT HTTP Server edition V2.5
V2.5 adds the following functions:

2.5 is more robust especially for POSTing from those "weird" network streams
2.5  includes new functionality and improvement to work with the new Database Jumpstart, Remote Reporter, and WebCalendar
add-ons
StatusQ has been changed to IFTStatusQ to avoid a possible problem with a similarly named structure in the ABC templates
IFTSend works much better now if you choose to use it when you don't know realy how big a request result will be.
FindReplace function has an option to toggle translation of either <br> or <13,10> as you see fit.
Stability has increased after getting rid of some little bugs that caused big problems. One of those bugs caused a false Content Length reading of 3 when there was not any content-length reading. This may have caused HTTP code to show up when POSTing data.
Added a new Display Log control template to the set. It's a nicer presentation for you so you can your server in action. So now you don't have to program a display log  or just have a window with just the Start/Stop controls.
*It is soooooo,  much, much, easier to web-enable your data fields when you use Database Jumpstart to IFT. This is serious point, click, see-your-data-on-the-web, in-a-quick-minute technology.  It is a must have.
*Remote Reporter will let your user see your custom reports anywhere. Working much better with IFT with new template mods.
*WebCalendar will give you a clean slick calendar interface to your data. Will work easily with Database Jumpstart as well with new template mods.
New demo app for IFT called zdemo1a.app
New demo for DBJ called zapdbj1.app
Both apps use the same dct file  called zdemo1.dct
 
 

Below are notes on changes in  the IFT HTTP Server edition V2.0
V2.0 adds the following functions:

New docs include: Below are notes on changes in  the IFT HTTP Server edition V1.5.

General Notes:
Lots of performance improvements (better for frames, graphics, etc), new functions, and bug fixes.
It comes with additional Templates (free to current customers) for server-side include techniques. These are
the beta MailMerge templates for Inserting text (srchrplc.tpl) and lists (mminline.tpl). Please install them for use with the new demo ZDEMO1.app. The About.htm (part of the demo) is the documentation so far, more later. They are the first Add-on products for IFT and I hope you find them interesting. More add-ons coming.

Please install all of the templates that come with the setup to see everything inthe demo. IN additionto the IFT there is MMINLINE.TPL, SRCHRPLC.TPL, and SIMPSHEX.TPL

Biggest Changes:
All of the templates go in the TEMPLATE directory (Notice the Search and Replace Templates I've included)
This rev should clear up the refresh or reload issue for lists and that pesky Error 02 WSINLST bug.

The functions are more parametrically driven than event driven. In other words where I had Post(Event:CloseClientSocket,,) it is now OnCloseClientSocket(ReqSocket)
 So you woud replace

Err=ssend(LOC_Client_ReqSocket, sendbuf, len(sendbuf),0)
Post(Event:CloseClientSocket,,)

with

Err=ssend(ReqSocket, sendbuf, len(sendbuf),0)
OnCloseClientSocket(ReqSocket)

in your code. A general rule wherever I had Post(Event:DoSomething) it is now OnDoSOmesomething PROCEDURE(ReqSocket, SOCKET, <ReqString STRING>). Please the docs for more details

The ZDEMO1.app is fairly comprehensive as to the various uses of the IFT. Please study it.

There is now an interface in global templates that lets you control throughput from the global.

Another is an improved IFTSEND for when you dont know how big your genrated string is going to be.
Set the variable size for sendbuf to something absurdly large and let IFTSEND handle the rest.

The new demo app, ZDEMO1.app, has the merge functions (Mergeinit for single text and InlineMergeinit for lists) in it to demo  features of the new MM templates. Tokens are replaced tokens with constant or variable data from formulas, file fields, etc... You predefine the tokens anyway you want (as far I know) and then you associate the tokens with the real data sources.

What this add-on means for IFT is you can define tokens in HTML generated by a 3rd party editor and have the IFT server turn it into dynamic data. Setup of this add-on has three primary steps and then a way you go. You'll want to use the defaullts on everything except the Data Associations (default is none).  Add a few lines of code as shown in the demos and then compile.

If you have Add-on ideas you would like to implement please let me know to see how I can help you.
(BTW, the HTTP Client is in alpha and on it's way)

Ok have fun.