Input: [Name] SPSTOC#0 [Title]

Output: Contents area Template

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSTOPIC#0 [Title]

Output: Topic area template

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSNEWS#0 [Title]

Output: News Site

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] CMSPUBLISHING#0 [Title]

Output: Publishing Site

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] BLANKINTERNET#0 [Title]

Output: Publishing Site

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] BLANKINTERNET#1 [Title]

Output: Press Releases Site

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] BLANKINTERNET#2 [Title]

Output: Publishing Site with Workflow

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSNHOME#0 [Title]

Output: News Site

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSSITES#0 [Title]

Output: Site Directory

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSCOMMU#0 [Title]

Output: Community area template

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSREPORTCENTER#0 [Title]

Output: Report Center

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSPORTAL#0 [Title]

Output: Collaboration Portal

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SRCHCEN#0 [Title]

Output: Enterprise Search Center

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] PROFILES#0 [Title]

Output: Profiles

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] BLANKINTERNETCONTAINER#0 [Title]

Output: Publishing Portal

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SPSMSITEHOST#0 [Title]

Output: My Site Host

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] ENTERWIKI#0 [Title]

Output: Enterprise Wiki

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SRCHCENTERLITE#0 [Title]

Output: Basic Search Center

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SRCHCENTERLITE#1 [Title]

Output: Basic Search Center

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] SRCHCENTERFAST#0 [Title]

Output: FAST Search Center

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Name] visprus#0 [Title]

Output: Visio Process Repository

Not every SharePoint site template supports Multilingual UI (MUI)! - SharePoint Use Cases


Input: [Parameter] min [Default] 0 [Description]

Output: Minimum number of connection pool entries, unrelated to the actual number of connections. This only needs to be modified from the default for special circumstances where heap memory associated with the backend connections should be preallocated or retained.


Input: [Parameter] max [Default] 1...n [Description]

Output: Maximum number of connections that will be allowed to the backend server. The default for this limit is the number of threads per process in the active MPM. In the Prefork MPM, this is always 1, while with other MPMs it is controlled by the ThreadsPerChild directive.


Input: [Parameter] smax [Default] max [Description]

Output: Retained connection pool entries above this limit are freed during certain operations if they have been unused for longer than the time to live, controlled by the ttl parameter. If the connection pool entry has an associated connection, it will be closed. This only needs to be modified from the default for special circumstances where connection pool entries and any associated connections which have exceeded the time to live need to be freed or closed more aggressively.


Input: [Parameter] acquire [Default] - [Description]

Output: If set this will be the maximum time to wait for a free connection in the connection pool, in milliseconds. If there are no free connections in the pool the Apache will return SERVER_BUSY status to the client.


Input: [Parameter] connectiontimeout [Default] timeout [Description]

Output: Connect timeout in seconds. The number of seconds Apache waits for the creation of a connection to the backend to complete. By adding a postfix of ms the timeout can be also set in milliseconds.


Input: [Parameter] disablereuse [Default] Off [Description]

Output: This parameter should be used when you want to force mod_proxy to immediately close a connection to the backend after being used, and thus, disable its persistent connection and pool for that backend. This helps in various situations where a firewall between Apache and the backend server (regardless of protocol) tends to silently drop connections or when backends themselves may be under round- robin DNS. To disable connection pooling reuse, set this property value to On.


Input: [Parameter] flushpackets [Default] off [Description]

Output: Determines whether the proxy module will auto-flush the output brigade after each "chunk" of data. 'off' means that it will flush only when needed, 'on' means after each chunk is sent and 'auto' means poll/wait for a period of time and flush if no input has been received for 'flushwait' milliseconds. Currently this is in effect only for AJP.


Input: [Parameter] flushwait [Default] 10 [Description]

Output: The time to wait for additional input, in milliseconds, before flushing the output brigade if 'flushpackets' is 'auto'.


Input: [Parameter] keepalive [Default] Off [Description]

Output: This parameter should be used when you have a firewall between your Apache and the backend server, who tend to drop inactive connections. This flag will tell the Operating System to send KEEP_ALIVE messages on inactive connections and thus prevent the firewall to drop the connection. To enable keepalive set this property value to On. The frequency of initial and subsequent TCP keepalive probes depends on global OS settings, and may be as high as 2 hours. To be useful, the frequency configured in the OS must be smaller than the threshold used by the firewall.


Input: [Parameter] lbset [Default] 0 [Description]

Output: Sets the load balancer cluster set that the worker is a member of. The load balancer will try all members of a lower numbered lbset before trying higher numbered ones.


Input: [Parameter] ping [Default] 0 [Description]

Output: Ping property tells webserver to send a CPING request on ajp13 connection before forwarding a request. The parameter is the delay in seconds to wait for the CPONG reply. This features has been added to avoid problem with hung and busy Tomcat's and require ajp13 ping/pong support which has been implemented on Tomcat 3.3.2+, 4.1.28+ and 5.0.13+. This will increase the network traffic during the normal operation which could be an issue, but it will lower the traffic in case some of the cluster nodes are down or busy. Currently this has an effect only for AJP. By adding a postfix of ms the delay can be also set in milliseconds.


Input: [Parameter] loadfactor [Default] 1 [Description]

Output: Worker load factor. Used with BalancerMember. It is a number between 1 and 100 and defines the normalized weighted load applied to the worker.


Input: [Parameter] redirect [Default] - [Description]

Output: Redirection Route of the worker. This value is usually set dynamically to enable safe removal of the node from the cluster. If set all requests without session id will be redirected to the BalancerMember that has route parameter equal as this value.


Input: [Parameter] retry [Default] 60 [Description]

Output: Connection pool worker retry timeout in seconds. If the connection pool worker to the backend server is in the error state, Apache will not forward any requests to that server until the timeout expires. This enables to shut down the backend server for maintenance, and bring it back online later. A value of 0 means always retry workers in an error state with no timeout.


Input: [Parameter] route [Default] - [Description]

Output: Route of the worker when used inside load balancer. The route is a value appended to session id.


Input: [Parameter] status [Default] - [Description]

Output: Single letter value defining the initial status of this worker: 'D' is disabled, 'S' is stopped, 'I' is ignore-errors, 'H' is hot-standby and 'E' is in an error state. Status can be set (which is the default) by prepending with '+' or cleared by prepending with '-'. Thus, a setting of 'S-E' sets this worker to Stopped and clears the in-error flag.


Input: [Parameter] timeout [Default] ProxyTimeout [Description]

Output: Connection timeout in seconds. The number of seconds Apache waits for data sent by / to the backend.


Input: [Parameter] ttl [Default] - [Description]

Output: Time to live for inactive connections and associated connection pool entries, in seconds. Once reaching this limit, a connection will not be used again; it will be closed at some later time.


Input: [Type] Menu [Usage] type= "menu" [Description]

Output: Menu integrated into the button with small arrow icon

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Type] Dual Menu [Usage] type= "menu-button" [Description]

Output: Menu appears distinct from the button, in separate clickable area

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Type] Checkbox [Usage] type= "checkbox" [Description]

Output: When selected, remains in a depressed state and toggles back to its natural state when selected again

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Type] Radio [Usage] type= "radio" [Description]

Output: Designed to be part of a group; only one button is selectable at a time

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Type] Disclosure [Usage] dlgtype= "disclosure" [Description]

Output: Shows/Hides a portion of a dialog window

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Type] Default [Usage] dlgtype= "accept" [Description]

Output: Performs the default action for a dialog

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Type] Cancel [Usage] dlgtype= "cancel" [Description]

Output: Closes the dialog and does not carry out the default action

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Type] Help [Usage] dlgtype= "help" [Description]

Output: Activates context-sensitive help

Creating Applications with Mozilla - Chapter 3: XUL Elements and Features

Table 3-3: Button types


Input: [Key] , [Bindings]

Output: Rotate between sorting modes


Input: [Key] s i [Bindings]

Output: Reverse current sorting order


Input: [Key] s a [Bindings]

Output: Sort buffers by alphabet


Input: [Key] s f [Bindings]

Output: Sort buffers by filename


Input: [Key] s v [Bindings]

Output: Sort buffers by last viewing time


Input: [Key] s s [Bindings]

Output: Sort buffers by size


Input: [Key] s m [Bindings]

Output: Sort buffers by major modes


Input: [Method] hasCss [Return] true|false [Description]

Output: Determine if the bridge is loaded with some CSS-stylesheets


Input: [Method] hasJs [Return] true|false [Description]

Output: Determine if the bridge is loaded with some JavaScript-scripts


Input: [Method] hasPrototypeJs [Return] true|false [Description]

Output: Determine if the bridge is loaded with Prototype JavaScript


Input: [Method] removeMagentoScripts [Return] null [Description]

Output: Try to remove all Magento scripts from the current page


Input: [Method] addMagentoStylesheet [Argument] * [Return] null [Description]

Output: Add a Magento stylesheet to the page


Input: [Method] isLoaded [Return] true|false [Description]

Output: Sees whether either the MageBridge component or a MageBridge module is loaded


Input: [Method] isMobile [Return] true|false [Description]

Output: Determine whether Joomla! detects the current browser as a mobile browser


Input: [Method] hasModule [Argument] string [Return] true|false [Description]

Output: Checks whether a specific module (example: mod_magebridge_block) appears on the page


Input: [Method] countModules [Return] true|false [Description]

Output: Copy of the original method, but now skipping modules that have empty content


Input: [Method] allowPosition [Argument] string [Return] true|false [Description]

Output: See whether a certain module-position (left, right) is flushed in the MageBridge configuration or not


Input: [Method] getRootTemplate [Return] true|false [Description]

Output: Get the current page layout


Input: [Method] getPageLayout [Return] string [Description]

Output: Alternative for getRootTeplate


Input: [Method] getHandles [Return] array [Description]

Output: Get an array of all Magento XML-handles


Input: [Method] hasHandle [Argument] string [Return] true|false [Description]

Output: Check for a specific Magento XML-handle


Input: [Method] hasLeftColumn [Return] true|false [Description]

Output: Determine if the Magento theme is using the left-column layout


Input: [Method] hasRightColumn [Return] true|false [Description]

Output: Determine if the Magento theme is using the right-column layout


Input: [Method] hasAllColumns [Return] true|false [Description]

Output: Determine if the Magento layout uses all three columns (main component plus left plus right)


Input: [Method] hasTwoColumns [Return] true|false [Description]

Output: Determine if the Magento layout uses two columns (main component plus one side-column)


Input: [Method] hasOneColumn [Return] true|false [Description]

Output: Determine if the Magento layout uses only one column (main component)


Input: [Method] getRequest [Return] string [Description]

Output: Get the current Magento page-request


Input: [Method] getStore [Return] string [Description]

Output: Get the current Magento store-code


Input: [Method] isHomePage [Return] true|false [Description]

Output: Determine if the current request is the homepage


Input: [Method] isPage [Argument] string [Return] true|false [Description]

Output: Determine if the current request is a specific page


Input: [Method] isCatalogPage [Return] true|false [Description]

Output: Determine if the current request is a catalog page


Input: [Method] isProductPage [Return] true|false [Description]

Output: Determine if the current request is a catalog product page


Input: [Method] isCategoryPage [Return] true|false [Description]

Output: Determine if the current request is a catalog category page


Input: [Method] isCustomerPage [Return] true|false [Description]

Output: Determine if the current request is a customer page


Input: [Method] isCheckoutPage [Return] true|false [Description]

Output: Determine if the current request is a checkout page


Input: [Method] isCartPage [Return] true|false [Description]

Output: Determine if the current request is the shopping cart


Input: [Method] isSalesPage [Return] true|false [Description]

Output: Determine if the current request is a sales-page


Input: [Method] isWishlistPage [Return] true|false [Description]

Output: Determine if the current request is a wishlist-page


Input: [Method] getProductId [Return] true|false [Description]

Output: Get the currently active product-ID from Magento


Input: [Method] getCategoryId [Return] integer [Description]

Output: Get the currently active category-ID from Magento


Input: [Method] isCategoryId [Argument] integer [Return] true|false [Description]

Output: Check whether current category-ID matches (including subcategories)


Input: [Endpoint] PUT /v1//queues/ [1]

Output: Creates a new queue


Input: [Endpoint] POST /v1//queues//messages [1]

Output: Pushes a message to a queue


Input: [Endpoint] GET /v1//queues//messages [1]

Output: Pops messages from a queue


Input: [Endpoint] GET /v1//queues/ [1]

Output: Get details of a queue


Input: [Endpoint] GET /v1//queues [1]

Output: Lists all queues


Input: [Endpoint] DELETE /v1//queues//messages/ [1]

Output: Deletes a message from a queue


Input: [Endpoint] DELETE /v1//queues/ [1]

Output: Deletes a queue


Input: [Command] ls [Description]

Output: List files in the current directory


Input: [Command] cd [Description]

Output: Change directory


Input: [Command] more [Description]

Output: View a file's contents


Input: [Command] mkdir [Description]

Output: Create a directory


Input: [Command] cp file1 file2 [Description]

Output: Copy a file


Input: [Command] mv file1 file2 [Description]

Output: Move (i.e. rename) a file


Input: [Command] rm file [Description]

Output: Delete a file


Input: [Command] rmdir dir [Description]

Output: Delete an empty directory