AO Logo
 
 English Japanese
  
  
  
Developer Tools
Life Cycle
Company Info
AOServ Platform
Services
Data Centers
Articles
Client Area
Contact Us
AO
AO Industries, Inc.
Application Infrastructure ProviderApplication Infrastructure Provider
Sign Up What's New Client Area Contact Us Site Map
 
your location:   home page···what's new
What's New
See What's Old instead.

Date Description
2018-08-13

We now support Python 3.7.

Python 3.7 may be used for any existing user or application by updating your profile script to include /opt/python-3.7/profile.sh (for Bourne shells) or /opt/python-3.7/profile.csh (for C shells).

2018-08-13

We now support Python 3.6.

Python 3.6 may be used for any existing user or application by updating your profile script to include /opt/python-3.6/profile.sh (for Bourne shells) or /opt/python-3.6/profile.csh (for C shells).

2018-08-13

We now support Python 3.5.

Python 3.5 may be used for any existing user or application by updating your profile script to include /opt/python-3.5/profile.sh (for Bourne shells) or /opt/python-3.5/profile.csh (for C shells).

2018-08-13

We now support Python 3.4.

Python 3.4 may be used for any existing user or application by updating your profile script to include /opt/python-3.4/profile.sh (for Bourne shells) or /opt/python-3.4/profile.csh (for C shells).

Please note that Python 3.4 End-of-life is 2019-03-16. Please consider going to Python 3.5, Python 3.6, or Python 3.7 now.

2018-07-29

We now support Java 10.

Java 10 may be used for any existing site by updating your profile script to include /opt/jdk-10/profile.sh. See this FAQ for more details on how to change Java versions:

https://aoindustries.com/clientarea/FAQ.ao?category=jvms&page=profile

As this is a non-LTS version, Java 10 will be supported until Java 11 is available. At that time, all uses of Java 10 will be automatically updated to Java 11.

This will be our last version using the commercial build from Oracle. In the next version, Java 11 LTS, we will be switching to the OpenJDK builds.

Due to Java version numbers no longer beginning with "1.", along with the introduction of "LTS" (long-term support) and non-LTS versions, we have split our jdk1 meta-package into jdk-lts (favoring stability by using the oldest supported LTS Java release) and jdk-current (favoring features by always having the most current Java release).

Any uses of /opt/jdk1/profile.* must be updated to either /opt/jdk-lts/profile.* or /opt/jdk-current/profile.*, depending on your choice of stability versus features.

For all managed servers, we are replacing /opt/jdk1/profile.* with /opt/jdk-lts/profile.*, as the LTS versions best match our previous release cycle. Likewise, new instances of Apache Tomcat will default to jdk-lts.

2018-07-27

We now support Tomcat 9.0 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver 8.0.*.

2018-07-27

We now support Tomcat 8.5 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver 8.0.*.

2018-07-17

We now support PHP 7.2. We have compiled PHP against PostgreSQL 10.

2018-07-17

We now support PHP 7.1. We have compiled PHP against PostgreSQL 9.6.

We have removed mcrypt from the build because it is deprecated in PHP 7.1. If this extension is required by your application, please Contact Us.

2018-07-17

We now support PHP 7.0. We have compiled PHP against PostgreSQL 9.4.

We now build with mysqlnd instead of depending on MySQL native libraries.

We have removed the dbase extension from this build. If this extension is required by your application, please Contact Us.

In this build, we have made the following changes to extension versions:

  1. memcached extension is now 3.*
  2. propro extension is now 2.*
  3. raphf extension is now 2.*
  4. HTTP extension is now 3.*

Older applications may need to be updated for these extension version changes before switching to PHP 7.0.

For both efficiency and security, we have switched to a more modular build of PHP, where some of the built-in extensions are built as shared libraries, packaged as separate RPMs, and only installed and enabled as-needed on a per-Apache/per-site basis. This means some extensions that were on by default in PHP 5 are now off by default in PHP 7.

We moved the default php.ini file from /opt/php-X.Y/lib/php.ini to /etc/opt/php-X.Y/php.ini, where X and Y are the major and minor versions, respectively.

We have also enabled Scan Directories with a default of /etc/opt/php-7.0/conf.d. For mod_php, this is overridden to /etc/httpd/conf/php[@instance]/conf.d for per-Apache configuration. For CGI, this is overridden to /var/www/site_name/webapps/ROOT/cgi-bin/php.d for per-site configuration.

2018-07-16

We now support MySQL 8.0.

2018-07-15

We now support PostgreSQL 10. We have included the following modules in our build:

  1. cube - Used by the earthdistance module.
  2. earthdistance - Allows spatial indexing of geographical coordinates - (latitude, longitude) pairs.
2018-07-15

We now support PostgreSQL 9.6. We have included the following modules in our build:

  1. cube - Used by the earthdistance module.
  2. earthdistance - Allows spatial indexing of geographical coordinates - (latitude, longitude) pairs.
  3. tsearch2 - Backwards compatibility for applications developed for versions of PostgreSQL prior to 8.3.
2018-07-14

We now support PostgreSQL 9.5. We have included the following modules in our build:

  1. cube - Used by the earthdistance module.
  2. earthdistance - Allows spatial indexing of geographical coordinates - (latitude, longitude) pairs.
  3. tsearch2 - Backwards compatibility for applications developed for versions of PostgreSQL prior to 8.3.
2016-07-21

Created a new servlet filter to automatically strip invalid XML characters from all inputs. GET requests are 301 redirected to a URL with the characters stripped. POST, and all other methods, are simply filtered and passed along to the rest of the application.

We have added this new filter to all JSP-based web applications we are currently maintaining.

Please see com.aoindustries.servlet.filter.StripInvalidXmlCharactersFilter for more information.

2016-07-20

Separated our set of reusable servlet filters into their own project. Please see the new ao-servlet-filter project at Downloads.

2016-03-05

The default Tomcat maxPostSize setting of 2 MiB is too small for real-world data, such as pictures from modern digital cameras. We have specified a maxPostSize of 16 MiB for all Tomcat 6, 7, and 8 installations.

Please see Apache Tomcat 8 Configuration Reference, Common Attributes for more information.

2016-01-08

We now support PHP 5.6 in both 32-bit and 64-bit builds. We have compiled PHP against PostgreSQL 9.4 and MySQL 5.7.

In this build we have switched to the 2.* version of the HTTP extension. Older applications may need to be updated for this change before switching to PHP 5.6.

2016-01-07

We now support MySQL 5.7 in both 32-bit and 64-bit builds.

2016-01-06

We now support Tomcat 8.0 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver.

2016-01-05

We now support PostgreSQL 9.4 in both 32-bit and 64-bit builds. We have included the following modules in our build:

  1. cube - Used by the earthdistance module.
  2. earthdistance - Allows spatial indexing of geographical coordinates - (latitude, longitude) pairs.
  3. tsearch2 - Backwards compatibility for applications developed for versions of PostgreSQL prior to 8.3.
2015-02-18

We are now using Stripe for our credit card processing. Sage Payments has served us well over the years and may remain a good option for some merchants, but we are attracted to the more predictable fee structure of Stripe.

2015-02-12

Our family of sites are now all running 100% over HTTPS. Previous releases of our system supported a mixture of HTTP and HTTPS. Now all communication is encrypted for maximum security.


See What's Old instead.
Copyright © 2000-2018 AO Industries, Inc.