updated depraction notes

[catagits/Catalyst-Runtime.git] / lib / Catalyst / Delta.pod

diff --git a/lib/Catalyst/Delta.pod b/lib/Catalyst/Delta.pod
index c110f27..f98d843 100755 (executable)
--- a/lib/Catalyst/Delta.pod
+++ b/lib/Catalyst/Delta.pod
@@ -9,7 +9,16 @@ Catalyst releases.
 
 =head2 VERSION 5.90060+
 
-=head3 Support passing Bpdy filehandles directly to your Plack server.
+=head3 Deprecation of Catalyst::Utils::ensure_class_loaded
+
+Going forward we recommend you use L<Module::Runtime>.  In fact we will
+be converting all uses of L<Class::Load> to L<Module::Runtime>.  We will
+also convert L<Catalyst::Utils\ensure_class_loaded> to be based on
+L<Module::Runtime> to allow some time for you to update code, however at
+some future point this method will be removed so you should stop
+using it now.
+
+=head3 Support passing Body filehandles directly to your Plack server.
 
 We changed the way we return body content (from response) to whatever
 Plack handler you are using (Starman, FastCGI, etc.)  We no longer
@@ -64,8 +73,7 @@ additional performance when you don't need all the checks and constraints.
 We also deprecated setting the response body to an object that does 'read'
 but not 'getline'.  If you are using a custom IO-Handle like object for
 response you should verify that 'getline' is supported in your interface.
-You will get a first use warning for this error in your logs.  Unless we
-here this case is a major issue for people, we will be removing support
+Unless we here this case is a major issue for people, we will be removing support
 in a near future release of Catalyst.  When the code encounters this it
 will issue a warning.  You also may run into this issue with L<MogileFS::Client>
 which does read but not getline.  For now we will just warn when encountering
@@ -104,6 +112,7 @@ to support setting body to a simple value since this is possible, but at
 some future release a choice to use streaming indicates that you will do
 so for the rest of the request.
 
+
 =head2 VERSION 5.90053
 
 We are now clarifying the behavior of log, plugins and configuration during