| 30 | | <li><strong>Extremamente leve.</strong> Kohana não possui dependências de extensões PECL ou bibliotecas da PEAR. Large, monolithic libraries are avoided in favor of optimized solutions.</li> |
| 31 | | <li><strong>GET, POST, COOKIE, <em>and</em> SESSION arrays all work as expected.</strong> Kohana does not limit your access to global data, but offers filtering and <abbr title="Cross Site Scripting">XSS</abbr> protection.</li> |
| 32 | | <li><strong>True auto-loading of classes.</strong> True on-demand loading of classes, as they are requested in your application.</li> |
| 33 | | <li><strong>No namespace conflicts.</strong> All classes are suffixed to allow similar names between components, for a more coherent API.</li> |
| | 30 | <li><strong>Extremamente leve.</strong> Kohana não possui dependências de extensões PECL ou bibliotecas da PEAR. Bibliotecas gigantescas e monolíticas são evitadas a favor de otimizar as solucões desenvolvidas.</li> |
| | 31 | <li><strong>GET, POST, COOKIE <em>e</em> SESSION funcionam como esperado.</strong> Kohana não limita seu acesso aos dados globais, mas oferece filtros e protecão contra <abbr title="Cross Site Scripting">XSS (Cross Site Scripting)</abbr>.</li> |
| | 32 | <li><strong>Carregamento automático de classes.</strong>Estas são carregadas sob demanda, de acordo com o requerido.</li> |
| | 33 | <li><strong>Não existe conflitos de namespace.</strong> Todas as classes estão adequadas para permitir componentes com nomes similares, a favor de uma API mais coerente.</li> |
| 35 | | <li><strong>Library drivers and API consistency.</strong> Libraries can use different "drivers" to handle different external <abbr title="Application Programming Interface">API</abbr>s transparently. For example, multiple session storage options are available (database, cookie, and native), but the same interface is used for all of them. This allows new drivers to be developed for existing libraries, which keeps the API consistent and transparent.</li> |
| | 35 | <li><strong>Drivers e API consistente.</strong> Bibliotecas podem ter diferentes "drivers" para manipular to handle different external <abbr title="Application Programming Interface">API</abbr>s transparently. For example, multiple session storage options are available (database, cookie, and native), but the same interface is used for all of them. This allows new drivers to be developed for existing libraries, which keeps the API consistent and transparent.</li> |