Skip to main content

Posts

Showing posts from March, 2010

Environmental Threats- Computer Security

Introduction To gain high secure, a system must be concerned about the interference of natural matters too. The natural matters which affect the security of a computer system are called as ‘Environmental Threats’. Some of the e xamples for environmental threats can be categorized as extreme cold,heat,humidity,dust,rainfalls,earthquakes, floods, fires, hurricanes, snow, ice, mud slides and sink holes. Methods of mitigating Environmental Threats · Air filters should remove fine dust particles because outdoor dust is brought in on clothes and shoes · Air filters must be cleaned or replaced in a regular schedule. · Periodically air heating equipment should be turned on, even it isn’t needed. This is to incrementally burn off that would other wise accumulate and be converted to an appreciable amount of smoke, when the equipment is activated for the first time after a long time period. · Water detectors should be placed above and below a raised floor to monitor the rise of water level. ·

WSRP Specification

Introduction The WSRP specification defines a web service interface for interacting with presentation-oriented web services. Initial work was produced through the joint efforts of the Web Services for Interactive Applications (WSIA) and Web Services for Remote Portlets (WSRP) OASIS Technical Committees in September, 2003. It is an interoperability standard. It’s platform- and language-neutral. It’s all about requesting and transmitting chunks of HTML using SOAP. The purpose of the Web Services for Remote Portlets protocol is to provide a web services standard that allows for the "plug-n-play" of remote running portlets from disparate sources. Many sites allow registered users to personalize their view of the website by turning on or off portions of the webpage, or by adding or deleting features. This is sometimes accomplished by a set of portlets that together form the portal. WSRP defines how a portal can connect to a diverse set of information service providers usin

Java Portlet Specification

Introduction The Java Portlet Specification provides a standard for developing portal components with the Java programming language. This specification, originally released in October 2003 called as JSR168, is gaining popularity as not only a standard for traditional portals, but also as a framework for deploying 'plug-ins' for standard Web applications. Currently there are three Java Portlet Specifications as JSR168, JSR170 and JSR 286. JSR 168 JSR168 is a standard relating to portlets within Java-based portals. JSR168 defines a standard set of behavior for portlets and a standard interface that governs how portlets interact with the portlet container (typically a portal package) in which they are hosted. In simple way it defines a portlet specification, including a contract between the portlet container and the portlet. JSR 168 is defined by the Java Community Process (JCP) in October 2003. Goals of JSR168 • Define the runtime environment, or the portlet container for portlet

Portlet Standards

This is a topic researched by me for the literature survey of our final year group project. Overview Over the past few years, portals have evolved rapidly in the Internet space. They have helped businesses aggregate secure and personalized content and applications to the Web.Portlets used by portals function as pluggable user-interface components that provide a presentation layer to information systems. In the early days of portal development, little emphasis was placed on component interoperability or reuse. Why? Because portlet APIs for development or customization at that time were limited to a single portal product only. To overcome these problems, the Portlet Specification was started to provide interoperability between portlets and portals. Portlet Specification defines the contract between a compliant portlet container and portlets. It defines a common Portlet API and infrastructure that provides facilities for personalization, presentation, and security. This standardization al

Installing SVN on Windows

Install SVN Server The steps to install SVN on windows as a service are listed below. Download the latest Subversion Windows binary installer from svn windows binary installer download . At the time of writing, that's 1.67. Then install it. (It’s better to override the default install path and going with something shorter as C:\svn\). The SVN installer adds c:\svn\bin to the installation path and can launch a command prompt and start working with it immediately. Then create the first source repository using following command. svnadmin create "C:\svn\repository" Within that newly created ‘repository’ folder, uncomment the following lines in the conf/svnserve.conf file by removing the pound character from the start of each line: anon-access=none auth-access=write password-db=passwd Next, add some users to the conf/passwd file. Uncomment the default harry and sally users to play with, or add own users: harry=harryssecret sally=sallyssecret Then to install Subversion as a