PicLan-IP version 220.127.116.11 is a major relesae that addresses a number of areas. This document describes chages in version 18.104.22.168 thru 22.214.171.124.
Version 126.96.36.199 and later requires new authorization codes. Please email modular software at email@example.com to get a new code. Please include your current PicLan-IP serial number.
Allocating connection control block zeroAn ongoing timing bug involving deleting connection block number zero has had some defensive programming applied. The TCP/IP buffer layer will no longer allocate block zero. This will hopefully make this bug less likely to reappear.
A new feature providing for global error pages has been added.
The file WWW.CTRL,LOCAL.PAGES has been added that creates local content web pages that can be accessed from any virtual web server.
If you specify a URL path that begins with an ampersand '&', then the web server will use the WWW.CTRL,LOCAL.PAGES file instead of the file specified in the HTTP LISTEN=... line of the PLIP.CTRL CONFIG item.
This feature is also used to generate busy pages for mv/Web applications when a web repost hits a locked state.
Version 188.8.131.52 adds support for version 1.3 of General Automation's mvBase platform.
Version 184.108.40.206 has a number of changes designed to improve the performance of the email sub-system, particularily for customer generating a large number of outbound mail transactions:
- DNS processing has been enhanced to support full caching of MX and A records
- Mail database operations have been enhanced for faster processing when the mail queue is large
- Inverted cross-reference lists have been replaced with Smart-Tree BTREE indexes
- Outbound TCP/IP network connections have been recoded as non-blocking operations.
With versions prior to 220.127.116.11 on hosted platforms, outbound network connections were codes as blocking sockets. This would cause the communications engine to stall when making outbound network connections until those connections completed. This did not impact most users as inbound connections like SMTP/POP3 receive and HTTP server functions do not make outbound connections. Sending email and HTTP client functions do use outbound connections and users with large amounts of outbound email were impacted by this issue. It should be noted that this only effects hosted (Win95/98/NT and Unix) PicLan-IP platforms and native PicLan-IP platforms do not encounter this issue.
Version 18.104.22.168 no longer uses blocking connections for outbound TCP/IP connections. This makes PicLan-IP much more robust for large email, HTTP client, and outbound sockets applications.