Web Server Clause Samples

The Web Server clause defines the requirements and responsibilities related to the hosting and operation of a web server for a particular service or application. Typically, this clause outlines who is responsible for providing, maintaining, and securing the web server, as well as any technical specifications or uptime commitments. For example, it may specify that the service provider must ensure the server is operational 99.9% of the time and implement necessary security measures. The core function of this clause is to ensure clarity regarding web server management, thereby minimizing disputes and ensuring reliable service delivery.
POPULAR SAMPLE Copied 2 times
Web Server. 5.8.1 The parties agree to discuss establishing a relationship for developing and maintaining a Web Server, the terms and conditions of any such relationship to be separately agreed upon by the parties.
Web Server. The term "Web Server" shall mean all of the shared hardware and software located at OpenSite's location or at such other location as may be designated by OpenSite that are necessary to host the Auction Site and to make the Auction Site available to Client's Customers on the Internet.
Web Server. A Server that is configured to serve web pages and related content via the HTTP and/or HTTPS protocols;
Web Server. The web server is the internet presence for FIFC. It contains the home page, help files, ticker lookup, login forms and other html/cgi related files. SOFTWARE Typical of most websites, the FIFC quote site features an HTML interface with the user, but also makes use of innovative Java applets to provide financial market information to subscribers. FUNCTIONS THAT THE SYSTEM IS INTENDED TO PERFORM The FIFC quote system is intended only to provide a "window" between the financial markets and individual investors, there will no transactions involved. The system allows registered users to login using their individual Login ID and password in order to access real-time market information. (Users must register and provide the information that is required by the stock exchanges as well as credit card information in order to be eligible to use the service.)
Web Server. The Customer's service provider operates and manages the Customer's web servers. The requirements are answered if the system is delivered as a web application or with web services, for example APIs based on use of web services. No. Requirement Importance (O/H/M/L) Describe T 61 The Contractor should clarify which web server platforms the system supports, for example Microsoft IIS or Apache. H D T 62 If the system supports several web server platforms, the Contractor should clarify and provide recommendations with regard to web server platform, and document any pros and cons in terms of solution choice. H D T 63 The Contractor should clarify any additional components, for example .NET runtime, PHP or similar frameworks and third party components that are required to be installed on the system’s web server. H D T 64 The Contractor is asked to clarify mechanisms that secure the web server and contents from unauthorised access. H D No. Requirement Importance (O/H/M/L) Describe Note: This includes which security mechanisms that are activated, and which mechanisms that additionally may be activated.
Web Server. The term “Web Server” shall mean all of the shared hardware and software located at Clinipace’s location or at such other location as may be designated by Clinipace that are necessary to host the Tempo Website and to make the Tempo Website available to REDHILL Designees on the Internet.
Web Server. ▇▇▇▇▇▇ ▇▇▇▇, MD, PLLC reserves the right to collect general information regarding usage and users of this Website. The information we receive depends on what you do during your visit. Our web server collects and stores the following general information about you: • The name of the domain from which you access the Internet (for example, ▇▇▇.▇▇▇, if you are connecting from an America Online account); • Your computer’s name; • Your version of web browser; • The date and time you access our service; • The pages you visit; • The Internet address of the website from which you linked directly to us; • The name and release number of web browser software you are using. This information is collected automatically. It is used in an aggregate way to help us improve our Website and make it more useful to you. This information may be shared with a third-­‐party web analytics company. Also, we may share information in an aggregated, de-­‐identified form with third parties with whom we have a business relationship. Notwithstanding the above, ▇▇▇▇▇▇ ▇▇▇▇, MD, PLLC may collect personally identifiable information regarding users who voluntarily provide such information (e.g., patients who sign up for the MD-­‐HQ Patient Portal) as further discussed in Section 6 below.
Web Server. Processor: Quad Core E7310 Xeon, 1.6GHz or higher* Memory: 8 GB RAM Hard Disk: 60 GB 10K RPM** Network: 1-10Gbps Operating System: Microsoft Windows 2016 Server or higher with Windows IIS Remote Access (optional): DATABASE SERVER: Microsoft Windows Remote Desktop Connection or similar. Processor: Quad Core E7310 Xeon, 1.6GHz or higher* Memory: 16 GB RAM Hard Disk: 100-1,000 GB 10K RPM Network: 1-10Gbps. Operating System: Microsoft Windows 2016 Server or higher Database: Microsoft SQL Server 2016 or higher Remote Access (optional): Microsoft Windows Remote Desktop Connection or similar * We support similarly configured virtual environments and/or shared database servers, including cloud environments ** We require file storage to store mugshots, reports, etc. This storage can be mounted on Web Server, Database Server, or on any UNC addressable location. Typical installation requires 20-100GB of such storage.
Web Server. Is a web server required? If so, what web application is required (Apache or IIS)? What version? Are add-ins required?
Web Server. This PEIS was responsible for all the HRI aspects. It run a web server, which implements the web- based interface displayed on the tablet carried by Doro, as well as a speech recognition system, which was connected to a wireless microphone weared by the user during the tests. The main PEIS tuples used to interface with the rest of the Robot-Era system were: Requests for user interaction, in the form ws1.interaction.doro1.77.parameters, USER_SERVICE_REQUEST ws1.interaction.doro1.77.command, ON These are typically sent to the Web Server by the CPM. Requests for user notifications, in the form ws1.notification.doro1.77.parameters, OUTDOOR_READY ws1.notification.doro1.77.command, ON These are also typically sent by the CPM. Status feedback on previous requests, in the form ws1.interaction.doro1.77.state, COMPLETED These are typically sent by the Web Server to the CPM. Service requests initiated by the user, in the form service.463.request.type, LOAD_LAUNDRY service.463.request.requester, user These are typically sent by the Web Server to the CPM, and they are interpreted as goals by the CPM.