Abstract: A fence gate latch mechanism for a fence gate is presented having a gate post positioned adjacent a fence post such that a space is defined between the gate post and the fence post. The fence gate latch mechanism includes a base plate attached to a sidewall of the gate post or the fence post within the space and an L-shaped latching member pivotally attached to the base plate and having an upper arm and a lower arm operating as a latching mechanism, the L-shaped latching member being positioned in the space such that no portion of the L-shaped latching mechanism extends beyond a front or top surface of a gate.

Abstract: Enabling a web application to call at least one native function of a mobile device includes accessing the web application by a browser of the mobile device. The web application includes at least one GUI element. The mobile device operates a listener module that is a TCP/IP socket listener listening for an address including a localhost IP address and a port number. Upon selection of the GUI element, a cross domain HTTP request is submitted by the browser to the listener localhost IP address. The listener module receives the request and calls the at least one native function in dependence on the received request.

Abstract: Enabling a web application to call at least one native function of a mobile device includes accessing the web application by a browser of the mobile device. The web application includes at least one GUI element. The mobile device operates a listener module that is a TCP/IP socket listener listening for an address including a localhost IP address and a port number. Upon selection of the GUI element, a cross domain HTTP request is submitted by the browser to the listener localhost IP address. The listener module receives the request and calls the at least one native function in dependence on the received request.

Abstract: Enabling a web application to call at least one native function of a mobile device includes accessing the web application by a browser of the mobile device. The web application includes at least one GUI element. The mobile device operates a listener module that is a TCP/IP socket listener listening for an address including a localhost IP address and a port number. Upon selection of the GUI element, a cross domain HTTP request is submitted by the browser to the listener localhost IP address. The listener module receives the request and calls the at least one native function in dependence on the received request.

Abstract: Enabling a web application to call at least one native function of a mobile device includes accessing the web application by a browser of the mobile device. The web application includes at least one GUI element. The mobile device operates a listener module that is a TCP/IP socket listener listening for an address including a localhost IP address and a port number. Upon selection of the GUI element, a cross domain HTTP request is submitted by the browser to the listener localhost IP address. The listener module receives the request and calls the at least one native function in dependence on the received request.

Abstract: A client system associated with a user includes at least one hardware processor configured to initiate the following operations. A modified login page is received from a proxy hardware system. An asynchronous engine is loaded by a browser system executing on the client system and caused by a routine from the modified login page. A login process with an authentication profiling service is executed, using the asynchronous engine, to retrieve login information for a back-end server. The authentication process with the back-end server is completed using the asynchronous engine. The modified logic page is generated by the proxy hardware system by adding the routine to a login page being sent from the back-end server to the browser.

Abstract: Enabling a web application to call at least one native function of a mobile device includes accessing the web application by a browser of the mobile device. The web application includes at least one GUI element. The mobile device operates a listener module that is a TCP/IP socket listener listening for an address including a localhost IP address and a port number. Upon selection of the GUI element, a cross domain HTTP request is submitted by the browser to the listener localhost IP address. The listener module receives the request and calls the at least one native function in dependence on the received request.

Abstract: A client system associated with a user includes at least one hardware processor configured to initiate the following operations. A modified login page is received from a proxy hardware system. An asynchronous engine is loaded by a browser system executing on the client system and caused by a routine from the modified login page. A login process with an authentication profiling service is executed, using the asynchronous engine, to retrieve login information for a back-end server. The authentication process with the back-end server is completed using the asynchronous engine. The modified logic page is generated by the proxy hardware system by adding the routine to a login page being sent from the back-end server to the browser.

Abstract: For managing a database in a data-processing system, a polymorph table and a mapping structure are provided. The polymorph table includes a discrimination column and a total number of columns of each type equal to a maximum of the virtual columns of the type. The mapping structure stores information mapping each virtual column to a polymorph column of the same type. A virtual access request is received based on one of the virtual columns of one of the virtual tables. Selected mapping information is retrieved that maps each selected virtual column to one of the polymorph columns. The virtual access request is converted into a polymorph access request according to an identifier of the selected virtual table and the selected mapping information. The polymorph table is accessed according to the polymorph access request.

Abstract: A login page is sent, by a backend server system, to a browser executing on a client associated with a user; and an authentication process is performed by the backend server system with the client. The logic page is intercepted by a proxy, and a modified logic page is generated by the proxy by adding a routine to the logic page. The modified logic page is forwarded to the browser, and the routine causes the browser to loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete the authentication process.

Abstract: A backend server system includes at least one hardware processor configured to initiate and/or perform the following. A login page is sent to a browser executing on a client associated with a user; and an authentication process is performed with the client. The logic page is intercepted by a proxy, and a modified logic page is generated by the proxy by adding a routine to the logic page. The modified logic page is forwarded to the browser, and the routine causes the browser to loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete the authentication process.

Abstract: A backend server system includes at least one hardware processor configured to initiate and/or perform the following. A login page is sent to a browser executing on a client associated with a user; and an authentication process is performed with the client. The logic page is intercepted by a proxy, and a modified logic page is generated by the proxy by adding a routine to the logic page. The modified logic page is forwarded to the browser, and the routine causes the browser to loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete the authentication process.

Abstract: A login page is sent, by a backend server system, to a browser executing on a client associated with a user; and an authentication process is performed by the backend server system with the client. The logic page is intercepted by a proxy, and a modified logic page is generated by the proxy by adding a routine to the logic page. The modified logic page is forwarded to the browser, and the routine causes the browser to loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete the authentication process.

Abstract: A proxy hardware system includes at least one processor configured to initiate and/or perform the following. A login page being sent to a browser executing on a client associated with a user from a back-end server is intercepted. A routine is added to the login page to generate a modified login page. The modified login page is forwarded to the browser. The browser, upon executing the routine, loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete an authentication process with the back-end server.

Abstract: A login page being sent to a browser executing on a client associated with a user from a back-end server is intercepted. A routine is added to the login page to generate a modified login page. The modified login page is forwarded to the browser. The browser, upon executing the routine, loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete an authentication process with the back-end server.

Abstract: A login page being sent to a browser executing on a client associated with a user from a back-end server is intercepted. A routine is added to the login page to generate a modified login page. The modified login page is forwarded to the browser. The browser, upon executing the routine, loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete an authentication process with the back-end server.

Abstract: A proxy hardware system includes at least one processor configured to initiate and/or perform the following. A login page being sent to a browser executing on a client associated with a user from a back-end server is intercepted. A routine is added to the login page to generate a modified login page. The modified login page is forwarded to the browser. The browser, upon executing the routine, loads an asynchronous engine configured to execute a login process with an authentication profiling service to retrieve login information for the back-end server, and complete an authentication process with the back-end server.

Abstract: For managing a database in a data-processing system, a polymorph table and a mapping structure are provided. The polymorph table includes a discrimination column and a total number of columns of each type equal to a maximum of the virtual columns of the type. The mapping structure stores information mapping each virtual column to a polymorph column of the same type. A virtual access request is received based on one of the virtual columns of one of the virtual tables. Selected mapping information is retrieved that maps each selected virtual column to one of the polymorph columns. The virtual access request is converted into a polymorph access request according to an identifier of the selected virtual table and the selected mapping information. The polymorph table is accessed according to the polymorph access request.

Abstract: A method for establishing and maintaining a Single Sign-on between a reverse proxy and a back-end server can include instigating an authentication process through a browser for a user to obtain access to the back-end server, intercepting a login page from the back-end server at the reverse proxy and adding a routine thereto, thereby loading an asynchronous engine on the browser executing a login process with an authentication profiling service, in order to retrieve the login information for the back-end server, and completing the authentication process with the back-end to allow the user access the back-end server through the asynchronous engine.

Abstract: A method for establishing and maintaining a Single Sign-on between a reverse proxy and a back-end server can include instigating an authentication process through a browser for a user to obtain access to the back-end server, intercepting a login page from the back-end server at the reverse proxy and adding a routine thereto, thereby loading an asynchronous engine on the browser executing a login process with an authentication profiling service, in order to retrieve the login information for the back-end server, and completing the authentication process with the back-end to allow the user access the back-end server through the asynchronous engine.