memcached使用什么散列算法来散列密钥？(What hashing algorithm does memcached use to hash keys?)

 1）每个模块可以选择定义进入/ interface / theme / layouts /文件夹的布局文件。 您可以通过在模块的config.xml文件中指定布局来完成此操作，如下所示： 
 
<frontend>
    <layout>
        <updates>
            <jason_page>
                <file>jasonpage.xml</file>
            </jason_page>
        </updates>
    </layout>
</frontend>
 
 2）是的。 
 
 a）Magento的界面是使用后向性构建的。 模板和布局首先取自您选择的界面和主题，如果没有找到，将从基础中获取。 这允许您仅在定义创建新基础时从基础更改的那些内容。 
 
 b）如果使用块创建新模块，则将在config.xml中指定这些块的类路径： 
 
<global>
    <blocks>
        <jason_page>
            <class>Jason_Page_Block</class>
        </jason_page>
    </blocks>
</global>
 
 这将定义标记jason_page以引用您的块。 然后，在定义布局时，您将引用块作为： 
 
<block type='jason_page/blockname' as='blockname' name='blockname' />
 
 您的块将命名为： Jason_Page_Block_Blockname中的/app/code/local/Jason/Page/Block/Blockname.php 
 
 c）每次使用<reference>标签并添加一些子块时，它们会被添加到大树中。 确保使用不同的name / as块的标签，你会没事的。 如果名称相同，则可能会导致错误。 
 
 d）local.xml（在app / etc中）定义了站点的一些配置参数，例如数据库连接信息和加密密钥。 它与布局无关。 
 
 d第2部分）由于您定义了布局文件，包括它们的名称，因此您不应该引起冲突。 选择一个比Page更独特的模块名称就可以了。 如果您的模块与默认模块（例如Page）具有相同的名称，则在config.xml文件中声明文件时，请在文件前添加命名空间。 
 
 希望有所帮助！ 
 
 谢谢，乔 

1) Each module can choose to define layout files that go into the /interface/theme/layouts/ folder. You can accomplish this by specifying the layouts in your module's config.xml file like this:
 
<frontend>
    <layout>
        <updates>
            <jason_page>
                <file>jasonpage.xml</file>
            </jason_page>
        </updates>
    </layout>
</frontend>
 
2) Yes.
 
a) Magento's interface is built using descendency. Templates and layouts are first taken from your chosen interface and theme, and if not found there, will be taken from base. This allows you to define only those things that change from the base when creating a new them.
 
b) If you create a new module with blocks, you will specify the classpath for those blocks in your config.xml:
 
<global>
    <blocks>
        <jason_page>
            <class>Jason_Page_Block</class>
        </jason_page>
    </blocks>
</global>
 
This will define the tag jason_page to refer to your blocks. Then, when defining a layout, you will reference your blocks as:
 
<block type='jason_page/blockname' as='blockname' name='blockname' />
 
And your blocks will be named as: Jason_Page_Block_Blockname in /app/code/local/Jason/Page/Block/Blockname.php
 
c) Each time you use a <reference> tag and add some child blocks, they are added to the large tree as you say. Make sure to use different name/as tags for the blocks, and you'll be fine. If the name is identical, you will probably cause errors.
 
d) local.xml (in app/etc) defines some configuration parameters for your site, such as database connection information and encryption keys. it doesn't have to do with layouts.
 
d part 2) Since you define your layout files, including their names, it's up to you to not cause collisions. Choosing a module name more unique than Page would go far here. If you do have a module with the same name as a default module (e.g. Page), prefix the file with your namespace when declaring it in your config.xml file.
 
Hope that helps!
 
Thanks, Joe