PROPOSED SYSTEM

The proposed system is to maintain the conferences, live meetings, general body
meetings on the net. This system is to develop in a client/server environment. It aims to
do the following.

 Grouping: Grouping of selected users

 Support of multi conference
 By selecting the single user from the list, Talk can be achieved
 By selecting all the users in the list, Chat can be achieved

Need for conference management system project computerization:

Time plays an important role in today’s world. Any information is useful if
it is available on the right time. Quick and correct information at he right time needs
computerization. Many scientists’ engineers have to spend their valuable time to attend a
conference, which is going on a long distance place. For conference management system
project them even one second costs millions and millions of dollars. So this project will
help them to participate in the conferences.

The main concept of Global Communication is developing the conference on the

net. We can compare the Global Communication with the Telephone Conference.
Normally in Telephone Conference, there will be more than two users connected at a time
and all the users are able to here words from any one of the user. So implementing the
same concept on the Net is nothing but Global Communication.
This project is used to:
 Conduct conferences with their employees. So they can get online decisions from
employees from the different branches of the company.
 The another advantage is that the company is having branches throughout the country.
So this will help them to communicate business affairs of the company and live
 meetings and conferences between their directors. They can conduct board of
directors meeting.
 It will give On-line solutions from the superiors to the employees.

PLATFORM/PACKAGES SELECTED

WINDOWS NT:
Windows NT is an operating system developed by Microsoft.
Two versions of NT are available: a server version and a workstation version. Both share
the same architecture, but the server version is optimized for conference management
system project running server operations, while the workstation version is intended for
conference management system project client machines. Windows NT workstation is
focussed on providing a desktop operating system for conference management system
project solving complex business needs, offering performance for conference
management system project systems such as dual-processor workstation or
multiprocessor RISC servers.

Windows NT is a 32-bit operating system. It offers much greater data transfer speed than
a 16 bit operating system, both with in the processor and to peripherals, and it allows a
much larger memory space to be addressed, boosting performance even more. The larger
memory space means that 32-bit operating systems have the band width to offer other
processing advantages, such as the ability to run different applications in separate
memory spaces, perform multitasking and so on.

NT workstation requires a powerful system. A minimum configuration of a 486 PC with

16 Mbytes of RAM and 200 Mbytes of hard disk is recommended by the Microsoft.

Windows NT workstation uses pre-emptive multitasking, which allows users to run tasks
simultaneously, without losing system performance. Pre-emptive multitasking assigns
processing resources equally between all the applications that are running, slowing down
all of them equally.

Multitasking, which is provided by, NT is vital for conference management system

project taking advantage of multiprocessing. It allows different parts of a program to be
handled independently by the operating systems

Windows NT provides crash protection by running applications in separate address

spaces. NT protects system resources by giving each application a mirror of the system
resources within its own spaces. If the application crashes only the mirrored resources, is
affected, while the real system resources, continues to function.

NT meets the security certification requirements for conference management system

project users level security on access to a standalone workstation. Files, folders and
application can be made invisible to specific users. It also provides secure user profiles to
control access to the desktop applications and system configuration files. A transacted
file offers increased data protection. NT workstation comes with the most common
networking protocols, including Netware, TCP/IP, IPX/SPX/ SLIP and PPP. It also
scalable and runs on a variety of platforms.
As more powerful mainstream machines are developed, technologies created for
conference management system project NT workstation will migrate to Windows 95. The
advantage is this compatibility brings to customers an users are that applications can be
shared across the two operating systems, that training needs are reduced as ease of use is
increased and the that the larger volume of application leads to lower software and
support cost.

HTML:
To publish information for conference management system project global
distribution, one needs a universally understood language, a kind of publishing mother
tongue that all computers may potentially understand. The publishing language used by
the World Wide Web is HTML (Hyper Text Markup Language). HTML gives authors
the means to
Publish online documents with headings, text, tables, lists, photos, etc. Retrieve online
information via hypertext links, at the click of a button Design forms for conference
management system project conducting transactions with remote services, for conference
management system project use in searching for conference management system project
information, making reservations, ordering products etc. Include spread - sheets, video
clips, sound clips, and other applications directly in their documents.

A brief history of HTML:

 HTML was originally developed by Tim Berners-Lee while at CERN, and
popularized by the Mosaic browser developed at NCSA. During the course of the 1990s
it has blossomed with the explosive growth of the Web during this time. HTML has been
extended in a number of ways. The Web depends on Web page authors and vendors
sharing the same conventions for conference management system project HTML. This
has motivated joint work on specifications for conference management system project
HTML.

HTML 2.0 (November 1995) was developed under the aegis of the Internet Engineering
Task Force (IETF) to codify common practice in late 1994. HTML (1993) and
([HTML.30]) (1995) proposed much richer versions of HTML, despite never receiving
consensus in standards discussions, these drafts led to the adoption of new features. The
efforts of the World Wide Web Consortium’s HTML working group to codify common
practice in 1996 resulted in HTML 3.2 (January 1997). Most people agree that HTML
documents should work well across different browsers and platforms. Achieving
interoperability lowers costs to content providers since they must develop only one
version of a document. If the effort is not made, there is much greater risk that the Web
will devolve into a proprietary world of incompatible formats, ultimately reducing the
Web’s commercial potential for conference management system project all participants.

Tables:
Authors now have greater control over structure and layout (e.g. column
groups). The ability of designers to recommend column widths user agents to display
table data incrementally (as it arrives) rather than waiting for conference management
system project the entire table before rendering.

Compound documents:
HTML now offers a standard mechanism for conference management
system project embedding generic media objects and applications in HTML documents.
The OBJECT element (together with its more specific ancestor elements IMG and
APPLET provides a mechanism for conference management system project including
images, video, sound, mathematics, specialized applications, and other objects in a
document. It also allows authors to specify a hierarchy of alternate renderings for
conference management system project user agents that don’t support a specific
rendering.

Style sheets:
Style sheets simplify HTML markup and largely relieve HTML of the
responsibilities of presentation. They give both authors and users control over the
presentation of documents- font information, alignment, colors, etc.

Style information can be specified for conference management system project specific
elements or groups of elements either within an HTML document or in separate style
sheets. The mechanism for conference management system project associating a style
sheet with a document is independent of the style sheet language. Before the advent of
style sheets, authors had limited control over rendering HTML 3.2 included a number of
attributes and elements offering control over alignment, font size, and text color. Authors
also exploited tables and images as a means for conference management system project
laying out pages. The relatively long time it takes for conference management system
project users to upgrade their browsers, means that these features will continue to be used
for conference management system project some time. However, since style sheets offer
more powerful presentation mechanisms, the World Wide Web Consortium will
eventually phase out many of HTML’s presentation elements and attributes.

Scripting:
Through scripts, authors may create “smart forms” that react at users fill them
out. Scripting allows designers to create dynamic Web pages, and to use HTML as a
means to build networked applications. The mechanism provided to associate HTML
with scripts are independent of particular scripting languages.

Printing:
Sometimes, authors will want to make it easy for conference management
system project users to print more than just the current document. When documents form
part of a larger work, the relationships between them can be described using the HTML
LINK element or using W3C’s Resource Description Language.

Designing documents with HTML 4.0:

The following general principles are observed when working with HTML 4.0
Separate structure and presentation
HTML has its roots in SGML, which has always been a language for
conference management system project the specification of structural markup. As HTML
matures more and more of its presentational elements and attributes are being replaced by
other mechanisms, in particular style sheets. Experience has shown that separating the
structure of a document from its presentational aspects reduces the cost of serving a wide
range of platforms, media, etc., and facilities document revisions.

Accessibility To The Universal Wide |Web:

To make the Web more accessible to everyone, notably those with disabilities,
authors should consider how their documents, may be rendered on a variety of platforms,
speech-based browsers, Braille readers, etc. We do not recommend that designers limit
their creativity, only that they consider alternate renderings in their design. HTML offers
a number of mechanisms to this end (e.g., the alt attribute, the access key attribute, etc).

Furthermore, authors should keep in mind, that their documents may be reaching a far-off
audience with different computer configurations. In order for conference management
system project documents to be interpreted correctly, designers should include in their
document information about the natural language and direction of the text, how the
document is encoded, and other issues related to internationalization. Help user agents
with incremental rendering: By carefully designing their labels and making user of new
table features in HTML 4.0, designers can help users agents render documents more
quickly. Authors can learn how to design tables for conference management system
project incremental rendering.

JAVA SCRIPT:

JavaScript is a scripting language developed jointly by Sun and Netscape

and is meant for conference management system project the WWW. A scripting language
is a simple programming language designed to enable programmers to write useful
programs quickly. A script is a similar to a macro, which tells a program how to perform
a specific procedure.

JavaScript Facts:

 JavaScript Is Embedded Into HTML:

JavaScript code is usually embedded into a HTML document and is
 executed, within them. By itself JavaScript has no user interface. It relies on,
HTML to provide the means of interaction with the user. Most Java Script objects
have HTML tags they represent. JavaScript extends the capabilities of HTML by
providing events to HTML tags and provide event driven code to execute it.

 JavaScript Is Browser Dependent:

JavaScript depends on the Web browser to support it. If the browser does
not support it, JavaScript code will be ignored. Internet Explorer 3.0 and, Netscape
Navigator 2.0 onwards support JavaScript.

 JavaScript Is an Interpreted Language:

JavaScript is interpreted at runtime by the browser before it is executed it. It
is not compiled into a separate program like a .exe but remains part of the HTML
file.

 JavaScript Is a Loosely Typed Language:

JavaScript is very flexible compared to Java. You need not specify,
the data type of a variable while declaring it. Also you need not declare
Variables explicitly. It is perfectly legal to declare variable as and when you
require them.
 JavaScript Is an Object-Based Language:
JavaScript is an object-based language. You can work with objects,
That encapsulates data (properties) and behavior (method). However JavaScript
object model is instance-based and there is no inheritance. This is the basic
difference between an object oriented and an object-based language.
 JavaScript Is Event-Driven:
HTML objects such as buttons are enhanced to support event
handlers. You can specify the functionality of a button.
 JavaScript Is Not Java:
Java applet is stored in a separate file and connected to a HTML file
through the <applet> tag, and it is a strongly typed, object oriented compiled
language. JavaScript is loosely typed object based, interpreted language meant
to create scripts.
 JavaScript Is Multifunctional:
JavaScript can be used to
 Enhance HTML pages
 Develop client side applications
 Build to a certain extent client/server Web applications
 Create extensions to a Web server.
 Provide database connectivity without using CGI.

 JavaScript Is Evolving:
JavaScript evolved in December 1995. As the time goes buy,
JavaScript will be embedded and new features added to it.

 JavaScript Language Spans Contexts:

JavaScript can be used in server side Netscape LiveWire Pro
Environment and Microsoft’s Active X server frame work. It is not just a client
side scripting tool.

WEB Application Frame Work

 Client Side Frame Work

 Client Side Applications
 Smart Pro Support
  Data validation
 Creating Interactive Forms
 Client Side Lookup Tables
 State Maintenance

Using this approach is slow and lets more bugs creep into applications. Developing into two different development
languages requires the knowledge of two technologies. When we use JDBC we need to know only the Java
language, whereas when we use CGI we must use Java and another language.

Another reason to use JDBC is that it is noticeably faster than CGI approach. Using CGI usually requires
that you call another program that must be executed by the computer. This separate program then accesses the
database and processes the data, returning it to the calling program in a stream. This requires multiple levels of
processing, which in turn increases wait time as well s enables more bugs to appear. The following figure displays
how CGI program is executed.

Java Web Server CGI Script Database

Fig. Calling a CGI script.
Application
Whereas calling a CGI script involves actually executing a new script, usually through a web server,
executing a JDBC statement against the database requires only some sort of server that passes the SQL commands
through the database. This speeds up dramatically the time it takes to execute SQL statements. Whereas the CGI
script must actually connect to the database and process the results, the JDBC solution lets your Java application
have the connection to the database so that thew application can perform all of the processing. The following figure
displays how a JDBC statement is executed.

Java Application JDBC Server Database

Fig. Executing a JDBC statement

JDBC IS A LOW-LEVEL API AND A BASE FOR CONFERENCE MANAGEMENT SYSTEM PROJECT
HIGER-LEVEL APIs:

JDBC is a “low-level” interface, which means that it is used to invoke (or “call’) SQL commands directly.
It works very well in this capacity and is easier to use than other database connectivity. JDBC APIs were also
designed to be a base upon which to build higher-level interfaces and tools. A higher-level interface is “user-
friendly”, using a more understandable or more convenient API that is translated behind the scenes into a low-level
interface such as JDBC. At present, two kinds of higher-level APIs are under development on top of JDBC:

1. An embedded SQL for conference management system project Java: At least one vendor plans to build this.
DBMS implement SQL, a language designed specifically for conference management system project use with
databases. JDBC requires that SQL statements be passed as strings to Java methods. An embedded SQL
processor allows a programmer to instead mix SQL statements directly with Java: for conference management
system project ex: a Java variable can be SQL statement to receive or provide SQL mix into Java with JDBC
calls.
2. A direct mapping of a relational database tables to Java classes: JavaSoft and others have announced plans to
implement this. In this “object/relational” mapping, each row of the table becomes an instance of that class,
and each column value corresponds to an attribute of that instance. Programmers can then operate directly on
Java objects; the required SQL calls to fetch and store data are automatically generated “beneath the covers”.
More sophisticated mappings are also provided, for conference management system project example, where
rows of multiple tables are combined into Java class.

2.1 As interest in JDBC has grown, more developers have been working in JDBC based tools to make building
programs easier, as well. Programmers have also been writing applications that make accessing a database easier for
conference management system project the end-user. For conference management system project e.g., an application
might present a menu of database tasks from which to choose. After a task is selected, the application presents
prompts and blanks for conference management system project filling in information needed to carry out the
selected task. With the required input typed in, the application then automatically invokes the necessary SQL
command. With the help of such an application, users can perform database tasks even when they have little or no
knowledge of SQL syntax.

Software Details

Server Operation System

Windows NT Server

Client Operating System

Windows NT Work Station

Languages Used:
Java 2.0(Servlets, Jdbc, ODBC, JavaWebServer3.0)

Java Script,

HTML,

DataBase :

MSACCESS.
Column Definition Description
Empname
Char(20) Name of the Client

Dateandtime Date/Time Time of joining

Address Text Area of Emp

Occupation Text Designation

Organisation Text Company

Emailid Text(50) Mail id of the Client

Uid Text Userid for conference

management system project login

Pwd Text Password for conference

management system project login