X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FDelta.pod;h=398649ff8c87edef8f21c9f21bc0c54509a4d71d;hb=f9bdcfacb19ab17ed0b889ed6366272d8bf166fc;hp=ea0b7c57dedb8953f1cf7e6995078f1dc56f673d;hpb=fb29a8be9ea07959afcb1ce9e38f6d7d6238e97d;p=catagits%2FCatalyst-Runtime.git diff --git a/lib/Catalyst/Delta.pod b/lib/Catalyst/Delta.pod index ea0b7c5..398649f 100755 --- a/lib/Catalyst/Delta.pod +++ b/lib/Catalyst/Delta.pod @@ -9,6 +9,15 @@ Catalyst releases. =head2 VERSION 5.90060+ +=head3 Deprecate Catalyst::Utils::ensure_class_loaded + +Going forward we recommend you use L. In fact we will +be converting all uses of L to L. We will +also convert L to be based on +L 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 @@ -17,7 +26,7 @@ always use the streaming interface for the cases when the body is a simple scalar, object or filehandle like. In those cases we now just pass the simple response on to the plack handler. This might lead to some minor differences in how streaming is handled. For example, you -might notice that streaming starts properly supportubg chunked encoding when +might notice that streaming starts properly supporting chunked encoding when on a server that supports that, or that previously missing headers (possible content-length) might appear suddenly correct. Also, if you are using middleware like L and are using @@ -36,7 +45,7 @@ using one server but deploying using a different one, differences in what those server do with streaming should be noted. Please see note below about changes to filehandle support and existing -Plack middleware to aid in back compatibility. +Plack middleware to aid in backwards compatibility. =head3 Distinguish between body null versus undef. @@ -59,43 +68,42 @@ so we benefit from better collaboration with developers outside Catalyst, 3) In the future you'll be able to change or trim the middleware stack to get additional performance when you don't need all the checks and constraints. -=head3 Deprecation of Filehandle like objects that do read but not getline +=head3 Deprecate Filehandle like objects that do read but not getline 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 which does read but not getline. For now we will just warn when encountering such an object and fallback to the previous behavior (where L itself unrolls the filehandle and performs blocking streams). However -this backcompat will be removed in an upcoming release so you should either +this backwards compatibility will be removed in an upcoming release so you should either rewrite your custom filehandle objects to support getline or start using the middleware that adapts read for getline L. -=head3 Response->headers become readonly after finalizing +=head3 Response->headers become read-only after finalizing Once the response headers are finalized, trying to change them is not allowed (in the past you could change them and this would lead to unexpected results). -=head3 Offically deprecation of L +=head3 Officially deprecate L L is also officially no longer supported. We will -no long run test cases against this and can remove backcompat code for it -as deemed necessary for the evolution of the platform. You should simple -discontinue use of this engine, as L has been PSGI at the core -for several years. +no long run test cases against this and can remove backwards compatibility code for it +as deemed necessary for the evolution of the platform. You should simply +discontinue use of this engine, as L has been PSGI at the core for +several years. -=head2 Officially deprecate finding the PSGI $env anyplace other than Request +=head3 Officially deprecate finding the PSGI $env anyplace other than Request A few early releases of Cataplack had the PSGI $env in L. -Code has been maintained here for backcompat reasons. This is no longer -supported and will be removed in upcoming release, so you should update +Code has been maintained here for backwards compatibility reasons. This is no +longer supported and will be removed in upcoming release, so you should update your code and / or upgrade to a newer version of L -=head2 Deprecate setting Response->body after using write/write_fh +=head3 Deprecate setting Response->body after using write/write_fh Setting $c->res->body to a filehandle after using $c->res->write or $c->res->write_fh is no longer considered allowed, since we can't send @@ -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 @@ -232,7 +241,7 @@ Below is a brief list of features which have been deprecated in this release: =item MyApp->plugin method is deprecated, use L instead. -=item __PACKAGE__->mk_accessors() is supported for backward compatibility only, use Moose attributes instead in new code. +=item __PACKAGE__->mk_accessors() is supported for backwards compatibility only, use Moose attributes instead in new code. =item Use of Catalyst::Base now warns