Abstract: An exhaust treatment apparatus for treating exhaust gas flowing through an exhaust line housing from an upstream location to a downstream location in a downstream direction, the exhaust treatment apparatus comprising a ceramic filter body having a honeycomb structure of a plurality of intersecting porous ceramic walls extending from a first end to a second end in an axial direction and defining a plurality of channels extending in the axial direction, wherein a first transverse face at the first end comprises metal oxide particles affixed to a portion of the intersecting walls. The metal oxide particles may be affixed to the upstream end, or the downstream end, or both the upstream and downstream ends. Preferably the metal oxide particles provide reinforcement to the underlying portion of the walls, and of the honeycomb structure itself.

Abstract: A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Abstract: An exhaust treatment method and apparatus for treating an exhaust stream flowing through an exhaust line housing in a downstream direction, the apparatus comprising a first particulate filter, an SCR unit, and a second particulate filter downstream of the SCR unit, all serially positioned in the exhaust line.

Abstract: A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Abstract: A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Abstract: A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Abstract: An exhaust treatment apparatus for treating exhaust gas flowing through an exhaust line housing from an upstream location to a downstream location in a downstream direction, the exhaust treatment apparatus comprising a ceramic filter body having a honeycomb structure of a plurality of intersecting porous ceramic walls extending from a first end to a second end in an axial direction and defining a plurality of channels extending in the axial direction, wherein a first transverse face at the first end comprises metal oxide particles affixed to a portion of the intersecting walls. The metal oxide particles may be affixed to the upstream end, or the downstream end, or both the upstream and downstream ends. Preferably the metal oxide particles provide reinforcement to the underlying portion of the walls, and of the honeycomb structure itself.

Abstract: A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Abstract: A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Abstract: A system for video playback switching in response to changing network conditions. The system includes streaming, from a distribution device such as a server, respective index files for a low bit rate version and a high bit rate version of the video file, to remotely executing instantiations of a low bit rate media player and a high bit rate media. Playback of the video file is begun by the high bit rate media player receiving and playing the high bit rate version from the server. Upon an indication of impeded network conditions, a transition point is selected, wherein the transition point indicates where downloading of the high bit rate version stops and where downloading of the low bit rate version begins. The low bit rate media player is then positioned to begin playback at the transition point. The stream of the video file is then switched to the low bit rate player upon encountering the transition point.

Abstract: Described is a technology in which one application running in a browser can host another application (e.g., an advertisement) in an isolated manner that prevents the hosted application from accessing browser data, or data of any other hosted application (including the host). The host and/or hosted application may be a browser plug-in (e.g., Microsoft® Silverlight™) application. The host application privately instantiates a hidden plug-in, with that hidden plug-in's access to browser data disabled, and loads the hosted application in the hidden plug-in. A XAML tag element may be used to identify the hosted application, along with a rendering area for the hosted application. Content from the hosted application is composited with content from the host application when rendering. The host application may provide keywords to the hosted application, such as for selecting relevant advertisements, and/or may allow the hosted application to open a browser window to display associated website content.

Abstract: A method for filling of a beverage packaging includes in-line microwave assisted pasteurizing a beverage, vaporized hydrogen peroxide treating a packaging, vaporized hydrogen peroxide treating a drinking straw, positioning the vaporized hydrogen peroxide treated drinking straw in the vaporized hydrogen peroxide treated packaging, fixing the drinking straw inside the packaging, adjusting a temperature of the pasteurized beverage and cold filling the pasteurized beverage into the packaging with the fixed straw, and sealing the packaging.

Abstract: Described is a technology in which one application running in a browser can host another application (e.g., an advertisement) in an isolated manner that prevents the hosted application from accessing browser data, or data of any other hosted application (including the host). The host and/or hosted application may be a browser plug-in (e.g., Microsoft® Silverlight™) application. The host application privately instantiates a hidden plug-in, with that hidden plug-in's access to browser data disabled, and loads the hosted application in the hidden plug-in. A XAML tag element may be used to identify the hosted application, along with a rendering area for the hosted application. Content from the hosted application is composited with content from the host application when rendering. The host application may provide keywords to the hosted application, such as for selecting relevant advertisements, and/or may allow the hosted application to open a browser window to display associated website content.

Abstract: Described is a technology in which one application running in a browser can host another application (e.g., an advertisement) in an isolated manner that prevents the hosted application from accessing browser data, or data of any other hosted application (including the host). The host and/or hosted application may be a browser plug-in (e.g., Microsoft® Silverlight™) application. The host application privately instantiates a hidden plug-in, with that hidden plug-in's access to browser data disabled, and loads the hosted application in the hidden plug-in. A XAML tag element may be used to identify the hosted application, along with a rendering area for the hosted application. Content from the hosted application is composited with content from the host application when rendering. The host application may provide keywords to the hosted application, such as for selecting relevant advertisements, and/or may allow the hosted application to open a browser window to display associated website content.

Abstract: A system for video playback switching in response to changing network conditions. The system includes streaming, from a distribution device such as a server, respective index files for a low bit rate version and a high bit rate version of the video file, to remotely executing instantiations of a low bit rate media player and a high bit rate media. Playback of the video file is begun by the high bit rate media player receiving and playing the high bit rate version from the server. Upon an indication of impeded network conditions, a transition point is selected, wherein the transition point indicates where downloading of the high bit rate version stops and where downloading of the low bit rate version begins. The low bit rate media player is then positioned to begin playback at the transition point. The stream of the video file is then switched to the low bit rate player upon encountering the transition point.

Abstract: A method for video playback switching in response to changing network conditions. The method includes accessing a server to retrieve respective index files for a low bit rate version and a high bit rate version of the video file, and instantiating a low bit rate media player and a high bit rate media. Playback of the video file is begun by the high bit rate media player streaming the high bit rate version from the server. Upon an indication of impeded network conditions, a transition point is selected, wherein the transition point indicates where downloading of the high bit rate version stops and where downloading of the low bit rate version begins. The low bit rate media player is then positioned to begin playback at the transition point. Playback of the video file is then switched to the low bit rate player upon encountering the transition point.

Abstract: Method, apparatus, and system to control ammonia slip in a selective catalytic reduction (SCR) system. The method includes detecting an engine operation transition event, increasing NOx to the SCR catalyst, and decreasing a reductant dose. The system includes a controller to receive an engine transition signal, anticipate a temperature transition at the SCR catalyst in response to the engine transition signal, and cause a NOx increase in the exhaust gas stream to the SCR catalyst and a decrease of reductant to the SCR catalyst coinciding with the temperature transition at the SCR catalyst. The apparatus includes a NOx increase module to cause the NOx increase in the exhaust gas stream to the SCR catalyst in response to the engine transition signal. The apparatus also includes a reductant shut-off module configured to cause the reductant addition to the exhaust gas stream to turn off in response to the engine transition signal.

Abstract: Method, apparatus, and system to control ammonia slip in a selective catalytic reduction (SCR) system. The method includes detecting an engine operation transition event, increasing NOx to the SCR catalyst, and decreasing a reductant dose. The system includes a controller to receive an engine transition signal, anticipate a temperature transition at the SCR catalyst in response to the engine transition signal, and cause a NOx increase in the exhaust gas stream to the SCR catalyst and a decrease of reductant to the SCR catalyst coinciding with the temperature transition at the SCR catalyst. The apparatus includes a NOx increase module to cause the NOx increase in the exhaust gas stream to the SCR catalyst in response to the engine transition signal. The apparatus also includes a reductant shut-off module configured to cause the reductant addition to the exhaust gas stream to turn off in response to the engine transition signal.

Abstract: A method of controlling the operation of a particulate filter in an exhaust gas after-treatment system may comprise calculating a ratio of particulate loading rate to filter regeneration rate using a mass-based soot load estimation scheme and comparing the ratio of particulate loading rate to filter regeneration rate to a predetermined threshold value. The method may further comprise controlling operating conditions of the particulate filter to maintain the ratio of particulate loading rate to filter regeneration rate at a value above the predetermined threshold value.

Abstract: The present invention extends to methods, systems, and computer program products for promoting the creation and use of application components in applications by distributing the application components in an application store. An application store hosts application components in conjunction with applications which use the application components. The application store tracks which components an application uses to distribute proceeds of the sale of an application among the owners of the application and application components used in the application. The application store may also store augmentations to a development platform to enable a development platform to be augmented between releases of the development platform.