One Hat Cyber Team
Your IP :
216.73.216.80
Server IP :
194.44.31.54
Server :
Linux zen.imath.kiev.ua 4.18.0-553.77.1.el8_10.x86_64 #1 SMP Fri Oct 3 14:30:23 UTC 2025 x86_64
Server Software :
Apache/2.4.37 (Rocky Linux) OpenSSL/1.1.1k
PHP Version :
5.6.40
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
var
/
www
/
vhost
/
conference
/
View File Name :
index.php
<?php /** * @mainpage OCS API Reference * * Welcome to the OCS API Reference. This resource contains documentation * generated automatically from the OCS source code. * * The design of Open %Conference Systems is heavily structured for * maintainability, flexibility and robustness. For this reason it may seem * complex when first approached. Those familiar with Sun's Enterprise Java * Beans technology or the Model-View-Controller (MVC) pattern will note many * similarities. * * As in a MVC structure, data storage and representation, user interface * presentation, and control are separated into different layers. The major * categories, roughly ordered from "front-end" to "back-end," follow: * - Smarty templates, which are responsible for assembling HTML pages to * display to users; * - Page classes, which receive requests from users' web browsers, delegate * any required processing to various other classes, and call up the * appropriate Smarty template to generate a response; * - Action classes, which are used by the Page classes to perform non-trivial * processing of user requests; * - Model classes, which implement PHP objects representing the system's * various entities, such as Users, Articles, and Journals; * - Data Access Objects (DAOs), which generally provide (amongst others) * update, create, and delete functions for their associated Model classes, * are responsible for all database interaction; * - Support classes, which provide core functionalities, miscellaneous common * * As the system makes use of inheritance and has consistent class naming * conventions, it is generally easy to tell what category a particular class * falls into. * For example, a Data Access Object class always inherits from the DAO class, * has a Class name of the form [Something]%DAO, and has a filename of the form * [Something]%DAO.inc.php. * * To learn more about developing OCS, There are several additional resources * that may be useful: * - The docs/README document * - The PKP support forum at http://pkp.sfu.ca/support/forum * - The technical reference (and other documents), available at * http://pkp.sfu.ca/ocs_documentation * * @file index.php * * Copyright (c) 2000-2012 John Willinsky * Distributed under the GNU GPL v2. For full terms see the file docs/COPYING. * * @ingroup index * * Bootstrap code for OCS site. Loads required files and then calls the * dispatcher to delegate to the appropriate request handler. */ // $Id$ // Initialize global environment define('INDEX_FILE_LOCATION', __FILE__); require('lib/pkp/includes/bootstrap.inc.php'); // Serve the request $application =& PKPApplication::getApplication(); $application->execute(); ?>