The document discusses ColdFusion 10, the next version of the ColdFusion platform that is currently in public beta. It provides an overview of new features and changes in ColdFusion 10, including moving to Tomcat from JRun, improvements to security, administration, language features like closures, integration with Solr, Java, REST, HTML5, and web sockets. It encourages downloading the beta to provide feedback and highlights upcoming blog posts about ColdFusion 10 features.
4. ColdFusion 10
Currently in public beta
Along with an update to ColdFusion
Builder
NOT TALKING ABOUT:
Release Dates (spoiler: not today)
Prices
Editions
All of the above is way over my pay grade.
9. Server level
Tomcat replaces JRun
Various internal libraries updated (Hibernate, Axis, Solr,
etc)
Security improved
Lazy loading for ORM and Flex
10. Admin Improvements
Hot Fix Installer
Template Cache – By Folder
Clear Query Cache
File Browser
IP Addresses for Admin
Multiple new pages/fields related to other
features
17. Session Improvements
httpOnly on by default
Secure (default is false)
Domain
Timeout (days, -1 for killing session when
browser closes)
sessionInvalidate and sessionRotate
29. Solr
Dynamic custom fields (as many as you
want, even up to 11!)
ORM based search
Data Import Handler (no more cfquery)
Other misc things… (more languages for
example)
33. REST
RESTful web services are built to work best on the
Web. Representational State Transfer (REST) is an
architectural style that specifies constraints, such as the
uniform interface, that if applied to a web service induce
desirable properties, such as performance, scalability,
and modifiability, that enable services to work best on
the Web. In the REST architectural style, data and
functionality are considered resources and are accessed
using Uniform Resource Identifiers (URIs), typically
links on the Web. The resources are acted upon by using
a set of simple, well-defined operations. The REST
architectural style constrains an architecture to a
client/server architecture and is designed to use a
stateless communication protocol, typically HTTP. In the
REST architecture style, clients and servers exchange
representations of resources by using a standardized
interface and protocol.
From: http://download.oracle.com/javaee/6/tutorial/doc/gijqy.html
34. REST
Who cares what it is – we make it easy!
(Btw – I'm kidding. Mostly.)
Extensions to component, function,
argument, application.cfc, and the Admin
38. Web Sockets
Bidirectional communication
One client to all the rest
Server to all clients
Front end support via <cfwebsocket>
Back end support for defining listeners
43. What next?
You downloaded it already, right? I mean, it's a virtual
presentation, you don’t have to pretend to pay attention,
so I know you downloaded the bits while I spoke along
with doing some mining in World of Warcraft and a bit of
client work. Get to it!
Lots of blog entries: www.coldfusionbloggers.org