Examples of using The server-side in English and their translations into Japanese
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Programming
The server-side component is a Java™ Enterprise application that must be deployed in a web application server such as IBM WebSphere or Apache Tomcat.
It manages and stores the server-side configuration data of the apps and adapters.
The server-side Wikipedia software translates this into the appropriate HTML and hypertext links.
Adapters contain the server-side code of applications that are deployed on and serviced by Mobile Foundation.
MySQL is the database management system, and PHP is the server-side scripting language.
You can modify the server-side configuration of your apps and adapters without stopping the MobileFirst Server.
Antivirus management Allows the subscriber to change settings of the server-side protection of incoming and outgoing mail from viruses.
For example, let's say we have sessions on the server-side and we can access the connected user through req. session. user.
StatusCode will be also used to render the proper status code from the server-side.
Default configuration After your application gems are installed, the server-side component generates and symlinks configuration files and directories for your application.
Continue reading for the server-side setup, or jump to Client-side setup.
As mentioned, an application is configured on both the client-side and the server-side.
You develop the server-side of your application separately, in JavaTM or in JavaScript.
These tools can also be used to test the server-side components for performance, locks, and other scalability issues.
At the very least one needs to register the server-side JavaScript files in the web. config file.
This functionality is provided in the server-side Node. js SDK via a global event listener API which hooks into the Realm Object Server, allowing you to observe changes across Realms.
Gem bundling After your code is copied to all instances in your environment, the server-side component checks for the existence of a Gemfile.
The server-side MobileFirst OAuth TAI API is no longer required and was removed.
You develop the server-side of your application separately, in Java™ or in JavaScript.
In the case of form validation, any error checking done by the client-side script should be repeated by the server-side form processor.