WEB DESIGN PROGRAME

A Web design program is a computer program used to create, edit, and update web pages and websites. The purpose of such a program is to make it easier for the designer to work with page and site elements through a graphical user interface that displays the desired results, typically in a WYSIWYG manner, while removing the need for the designer to have to work with the actual code that produces those results (which includes HTML or HTML, CSS, JavaScript, and others). Examples of a web design program are Macro media Dream weaver, which is a commercial program, and Amaya, which is an open source program.

ONLINE PRODUCER

An online producer oversees the making of content for websites. Online producers are sometimes called content producers or online editors.

The online producer's responsibility is usually to create, edit and arrange the text, video, audio, images and other materials that may be included on a website. Online producers define and maintain the character of a website, as opposed to running it from a technical standpoint.

The role is distinct from that of web designer, developer or webmaster. While some online producers do have technical or design knowledge which complements their production skills, an online producer's usual task is to combine the output of designers and developers into an end product that will suit its users.

Finding ways to boost the popularity of a website and increase user activity may also be the online producer's responsibility, particularly if the website sells advertising space.

Many online producers have a background in journalism, or continue to work in journalism as online producers. For example, in radio or television, an online producer may work closely with an executive producer to meet a broadcast show's online needs.

WEB CACHES

Web caching is the caching of web documents (e.g., HTML pages, images) in order to reduce bandwidth usage, server load, and perceived lag. A web cache stores copies of documents passing through it; subsequent requests may be satisfied from the cache if certain conditions are met.

Types of Web caches

Web caches can be deployed in a variety of ways. User agent caches, such as those in web browsers, are private caches, operating on behalf of a single user. Intermediaries can also implement shared caches that serve more than one person.

Proxy caches, also known as forward proxy caches, are usually deployed by internet service providers, schools and corporations to save bandwidth. Interception proxy caches (sometimes called "transparent caches") are a variant that doesn't require clients to be explicitly configured to use them.

Gateway caches, sometimes known as reverse proxy caches, surrogate caches, or web accelerators, operate on behalf of the origin server, and to clients are indistinguishable from it. A number of gateway caches can work together to implement a Content Delivery Network.

Intermediaries that cache often perform other duties, such as user authentication and content filtering. Multiple caches can also be coordinated using peering protocols like Internet Cache Protocol and HTCP.

Controlling Web caches

HTTP defines three basic mechanisms for controlling caches: freshness, validation and invalidation.

* Freshness allows a response to be used without re-checking it on the origin server, and can be controlled by both the server and the client. For example, the Expires response header gives a date when the document becomes stale, and the Cache-Control: max-age directive tells the cache how many seconds the response is fresh for.
* Validation can be used to check whether a cached response is still good after it becomes stale. For example, if the response has a Last-Modified header, a cache can make a conditional request using the If-Modified-Since header to see if it has changed.
* Invalidation is usually a side effect of another request that passes through the cache. For example, if URL associated with a cached response subsequently gets a POST, PUT or DELETE request, the cached response will be invalidated.

WEB CALANDER ACCESS PROTOCOL

Web Calendar Access Protocol (WCAP) is a protocol for remote client-server calendar access and scheduling based on the XML, HTTP, iCalendar, and vCard Internet standards. WCAP was created for use with the product that eventually became Sun Java Calendar Server, but is also used by the open source Buni Meldware project [1]. WCAP uses simple HTTP GET commands for accessing iCalendar, Freebusy, TODO and vCard entries. WCAP responses are either the traditional text form or an "xml-ized" form of iCalendar/etc[2]. Several plugins exist including those for Mozilla Thunderbird[3], Novell Evolution[4] and Microsoft Outlook[5]. There is a competing protocol called CalDAV undergoing standardization.

WEB PAGE HIJACKING

Page hijacking is a form of search engine index spamming. It is achieved by creating a rogue copy of a popular website which shows contents similar to the original to a web crawler, but redirects web surfers to unrelated or malicious websites. Spammers can use this technique to achieve high rankings in result pages for certain key words.

Page hijacking is a form of cloaking, made possible because some web crawlers detect duplicates while indexing web pages. If two pages have the same content, only one of the URLs will be kept. A spammer will try to ensure that the rogue website is the one shown on the result pages.


Google hijacking

One form of this activity involves 302 server-side redirects on Google. Hundreds of 302 Google Jacking pages were said to have been reported to Google.[citation needed] While Google has not officially acknowledged that page hijacking is a real problem, several people have found to be victims of this phenomenon when checking the search engine rankings for their website.
Example of page hijacking

Suppose that a website offers difficult to find sizes of clothes. A common search entered to reach this website is really big t-shirts, which - when entered on popular search engines - made the website show up as the first result:

SpecialClothes
Offering clothes in sizes you cannot find elsewhere.
www.example.com

A spammer working for a competing company then creates a website that looks extremely similar to one listed and includes a special redirection script that redirects web surfers to the competitor's site, but shows the page to web crawlers. After several weeks, a web search for really big t-shirts then shows the following result:

Special Clothes
Offering clothes in sizes you cannot find elsewhere... at better prices!
WWW.example.net/
—Show Similar Pages—

Notice how .com changed to .net, as well as the new "Show Similar Pages" link.

When web surfers click on this result, they are redirected to the competing website. The original result was hidden in the "Show Similar Pages" section.

WEB PAGE EDITOR

An HTML editor is a software application for creating web pages. Although the HTML markup of a web page can be written with any text editor, specialized HTML editors can offer convenience and added functionality. For example, many HTML editors work not only with HTML, but also with related technologies such as CSS, XML and JavaScript or ECMAScript. In some cases they also manage communication with remote web servers via FTP and WebDAV, and version management systems such as CVS or Subversion.

Object editors

Some editors allow alternate editing of the source text of objects in more visually organized modes than simple color highlighting, but in modes not considered WYSIWYG. Some WYSIWYG editors include the option of using palette windows that enable editing the text-based parameters of selected objects. These palettes allow either editing parameters in fields for each individual parameter, or text windows to edit the full group of source text for the selected object. They may include widgets to present and select options when editing parameters. Adobe GoLive provides an outline editor to expand and collapse HTML objects and properties, edit parameters, and view graphics attached to the expanded objects.
WYSIWYG HTML editors

WYSIWYG HTML editors provide an editing interface which resembles how the page will be displayed in a web browser. Some editors, such as ones in the form of browser extensions allow editing within a web browser. Because using a WYSIWYG editor does not require any HTML knowledge, they are easier for an average computer user to get started with.

The WYSIWYG view is achieved by embedding a layout engine based upon that used in a web browser. The layout engine will have been considerably enhanced by the editor's developers to allow for typing, pasting, deleting and moving the content. The goal is that, at all times during editing, the rendered result should represent what will be seen later in a typical web browser.

While WYSIWYG editors make web design faster and easier; many professionals still use text editors, despite the fact that most WYSIWYG editors have a mode to edit HTML code by hand. The web was not originally designed to be a visual medium, and attempts to give authors more layout control, such as CSS, have been poorly supported by major web browsers. Because of this, code automatically generated by WYSIWYG editors frequently sacrifice file size and compatibility with fringe browsers, to create a design that looks the same for widely used desktop web browsers. This automatically generated code may be edited and corrected by hand. For more on subject, see Difficulties in achieving WYSIWYG below

WYSIWYM editors

What You See Is What You Mean (WYSIWYM) is an alternative paradigm to the WYSIWYG editors above. Instead of focusing on the format or presentation of the document, it preserves the intended meaning of each element. For example, page headers, sections, paragraphs, etc. are labeled as such in the editing program, and displayed appropriately in the browser.

WEB ACCELERATOR

A web accelerator is a proxy server that reduces web site access times. They can be a self-contained hardware appliance or installable software.


Web accelerators may use several techniques to achieve this reduction:

* They may cache recently or frequently accessed documents so they may be sent to the client with less latency or at a faster transfer rate than the remote server could.
* They may freshen objects in the cache ensuring that frequently accessed content is readily available for display.
* They may preemptively resolve host names present in a document (HTML or JavaScript) in order to reduce latency.
* They may prefect documents that are likely to be accessed in the near future.
* They may compress documents to a smaller size, for example by reducing the quality of images or by sending only what's changed since the document was last requested.
* They may optimize the code from certain documents (such as HTML or JavaScript).
* They may filter out ads and other undesirable objects so they are not sent to the client at all.
* They may maintain persistent TCP connections between the client and the proxy server.