created in the following file: D:\wwwroot\testdrive\protected\models\User.php If you have a ’db’ database connection, you can test it now with: $model=User::model()->find(); print_r($model); >> crud User array( // these attributes can be massively assigned in any scenario // that is not explicitly specified below ’attr1, attr2, ...’, * // these attributes can be massively assigned only in scenario 1 ’scenario1’ ’scenario1’ => ’attr2, attr3, ...’, * // these attributes can be massively assigned only in scenario 2 ’scenario2’ => ’attr1, attr3, ...’, ) I f t h e m od e l i s n ot s c e n ar i o- s e n s i t i v

created in the following file: D:\wwwroot\testdrive\protected\models\User.php If you have a ’db’ database connection, you can test it now with: $model=User::model()->find(); print_r($model); >> crud User array( // these attributes can be massively assigned in any scenario // that is not explicitly specified below ’attr1, attr2, ...’, * // these attributes can be massively assigned only in scenario 1 ’scenario1’ ’scenario1’ => ’attr2, attr3, ...’, * // these attributes can be massively assigned only in scenario 2 ’scenario2’ => ’attr1, attr3, ...’, ) I f t h e m od e l i s n ot s c e n ar i o- s e n s i t i v

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release

code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses ThreadPoolExecutor, hoping that at least some of these image operations release the GIL during processing. Note: The ProcessPoolExecutor is another alternative for long running tasks that do not release