When you say "The way PHP does things", are you referring to
the serilization of session information (see php link below).
Normally the session information on a single server (PHP) is
written to a file in a temporary session folder but can be
serialized to a database through custom session handlers.
As far as doing the same in ColdFusion, you probably want to
look at using J2EE Session Management which would let you serialize
the Session Scope and implement Session Swapping. The "Persistent
session failover in JRun" article below discusses some of this.
The end result is the same in that you have to serialize the
session state and then persist that data in a manner that is
accessible to any system in the cluster, so that on subsequent
hits, the user's session can be de-serialized.
Reference:
(PHP) Session Handling Functions
http://us.php.net/session
Stateful Session Clustering: Have Your Availability and Scale
It Too
http://www.devx.com/Java/Article/32603
ColdFusion and J2EE session management
http://livedocs.adobe.com/coldfusion/6.1/htmldocs/shared29.htm
Persistent session failover in JRun
http://livedocs.adobe.com/coldfusion/6/Using_ClusterCATS/config9.htm