Board logo

subject: A Little Information About Java [print this page]


Java design was begun by James Gosling, Mike Sheridan and Patrick Naughton in 1991. The Java language was to begin with named Oak. It was re-named Green and ultimately Java because of the enormous quantities of Java Coffee that the developers of the language are said to have drank.

James Gosling aimed to create a language that had a style that would be comfortable to C programmers.

The 5 primary guiding principles whilst developing the language were:

It ought to be simple, object oriented and familiar.

It must be robust and secure.

It ought to be portable.

It must execute with good performance.

It must be interpreted, threaded and dynamic.

Sun Microsystems unveiled java to the general public in 1995. The major internet browsers were fast to add the ability to run java applets inside pages and Java grew to become tremendously popular.

Uses of Java include playing online games, running small apps like a web page counter and publishing photographs to Facebook. Many innovative uses for Java have recently appeared or are on the horizon. Because of the wide array of uses for Java (J2EE, stand-alone applications, applets, servlets, and so on), Java profilers usually do not work well in every environment.

Java Applets are small applications that are normally embedded in web pages. A good example of a java applet would be the rippling water effect that used to be widely used in many web pages.

Java was built to be portable and it can perform equally well on every operating system so software only needs to be written once rather then distinct editions for different operating systems which simplifies and accelerates development life cycles.

One particular complaint of the early java versions has been its slow speed in comparison with some other languages although the addition of JIT compilers has significantly alleviated the problem.

Quite a few Android Applications are actually created primarily in a version of Java

As a consequence of the huge level of popularity and usefulness of Java it's often targeted by hackers that can take advantage of any security weak spots that they discover so application security is very important to prevent successful attacks and should be built in from the design stage.

Security testing techniques ought to be applied through the entire software development. They should look for any weeknesses or security holes that will leave the program open to attack.

A vulnerability is a weakness which can be either an implementation issue or a design flaw that may enable an attacker to cause harm or access information on the pc or network running the program. Common vulnerabilities include incorrectly closing database connections or poor validation of user input, dynamic construction of SQL statements, failure to carry out proper input validation or lack of output encoding.

Some of the more obvious protection against potential security issues in Java web applications could be as simple as enabling all possible security configurations in web.xml, always use paraemterized SQL statements and regularly perform security code reviews. Java and J2EE have in built security measures but it can be difficult to write any program without a few security weaknesses. These potential weak points should be planned for when coding with Java.

Java really is a powerful language with virtually unlimited applications and is certain to become more and more widely used.

by: Stuart Kelso




welcome to loan (http://www.yloan.com/) Powered by Discuz! 5.5.0