X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FUpgrading.pod;h=f2b6a02fe7d975216c806ca9bc8746aba8c0babb;hb=8ee06de7066f445f4f60cbf64ddbb2f6f2e5cd87;hp=b73f32ad0e758780a7f6f0eac43ba159c25f4282;hpb=27dad9301094f25bcedc66c476ec8b9d61521fb7;p=catagits%2FCatalyst-Runtime.git diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod index b73f32a..f2b6a02 100644 --- a/lib/Catalyst/Upgrading.pod +++ b/lib/Catalyst/Upgrading.pod @@ -8,12 +8,12 @@ The major change is that L now replaces most of the subclasses of L. If you are using one of the standard subclasses of L this should be a straightforward upgrade for you. It was a design goal for this release to be as backwardly compatible as possible. -However since L is different from L it would be -possible that edge case differences would exist. Therefore we recommend care -be taken with this upgrade and that testing should be greater than would be -the case with a minor point update. +However since L is different from L it is possible +that edge case differences exist. Therefore we recommend care be taken with +this upgrade and that testing should be greater than would be the case with a +minor point update. -It is highly recommended that you become familar with the L ecosystem +It is highly recommended that you become familiar with the L ecosystem and documentation. Being able to take advantage of L development and middleware is a major bonus to this upgrade. Documentation about how to take advantage of L by writing your own C<< .psgi >> file @@ -23,7 +23,7 @@ If you have created a custom subclass of L you will need to convert it to be a subclass of L. If you are using the L engine, L, this new -release supercedes that code. +release supersedes that code. If you are using a subclass of L that is aimed at nonstandard or internal / testing uses, such as L you should @@ -40,7 +40,7 @@ enough to use L. The engines that are build upon the various iterations of mod_perl, L and -L should be seemless upgrades and will +L should be seamless upgrades and will work using using L or L as required. @@ -63,13 +63,13 @@ myapp_cgi.pl script is already upgraded enough to use L. If you were using L then L is automatically loaded. -If you were customising your server script to pass opttions to the prefork engine, +If you were customising your server script to pass options to the prefork engine, then this is no longer supported. The recommended route to implement this functionality -is to write a simple .psgi file for your application, then use the L untility. +is to write a simple .psgi file for your application, then use the L utility. =head2 Upgrading the PSGI Engine -If you were using L this new release supercedes this +If you were using L this new release supersedes this engine in supporting L. By default the Engine is now always L. As a result, you can stop depending on L in your C. @@ -123,8 +123,8 @@ B: my $app = sub { MyCatalystApp->psgi_app(@_) }; # If you make ^^ this mistake, your app won't work, and will confuse the hell out of you! -You can now rename C<< script/myapp.psgi >> to C<< myapp.psgi >>, and the built-in -Catalyst scripts, and your test suite will start using your .psgi file. +You can now move C<< script/myapp.psgi >> to C<< myapp.psgi >> and the built-in +Catalyst scripts and your test suite will start using your .psgi file. B If you rename your .psgi file without these modifications, then any tests run via L will not be compatible with the new release, and will result in @@ -167,13 +167,13 @@ highly welcomed: =back -=head2 Using middleware +=head2 Specifying the engine in the call to ->setup -XXX Should this be here or elsewhere? +XXX FIXME -=head2 Making an app.psgi file +=head2 Plack functionality -=head2 Running with plackup? +See L. =head2 Tests in 5.89 @@ -182,8 +182,8 @@ Tests should generally work the same in Catalyst 5.89, however there are some di Previously, if using L and doing local requests (against a local server), if the application threw an exception then this exception propagated into the test. -This behaviour has been removed, and now a 500 response will be returned to the test. -This change unifies behaviour, to make local test requests behave similarly to remote +This behavior has been removed, and now a 500 response will be returned to the test. +This change unifies behavior, to make local test requests behave similarly to remote requests. =head1 Upgrading to Catalyst 5.80 @@ -198,7 +198,7 @@ issues upgrading to this release. Most issues found with pre-existing components have been easy to solve. This document provides a complete description of behavior changes which may cause compatibility issues, and of new Catalyst warnings which -be unclear. +might be unclear. If you think you have found an upgrade-related issue which is not covered in this document, please email the Catalyst list to discuss the problem. @@ -209,7 +209,7 @@ this document, please email the Catalyst list to discuss the problem. You can only apply method modifiers after the application's C<< ->setup >> method has been called. This means that modifiers will not work with methods -which run during the call to C<< ->setup >>. +run during the call to C<< ->setup >>. See L for more information about using L in your applications.