A shinning life

Sub/Addon/Parked Domains

2008-09-12T15:43:00.001+10:00

https://support.lunarpages.com/knowledge_bases/article/148

Sub/Addon/Parked Domains
What is the difference between a subdomain, parked domain and add on domain? Subdomains: A subdomain name points to a subfolder of the primary domain. For instance, cats.pets.com would point to a subfolder such as /cats under the primary domain of pets.com. Its content is separate from the main site so it can act like a separate site though usually it will have some relevance to the main site as you can see above. A subdomain can also be used on our system to redirect to somewhere else and create a shorter way to get there. For instance, mymail.mydomain.com could be redirected to http://mydomain.com/webmail/horde/ to get to webmail easier and force the use of the Horde webmail client. Unlimited subdomains come with each hosting account. Parked Domains (Aliases): A parked domain is an additional domain that points to the main directory of your account. You can park unlimited domains at no cost on both the Basic and Business plans. A parked domain will resolve to your primary domain name. Say your primary is domain1.com and you park domain2.com. In the address bar if you type domain2.com it will resolve to domain1.com but in the address bar you will see domain2.com. This is a parked domain. *Addon domains: An add on domain allows you to run a separate web site to your primary domain. When you create an add on domain it makes a folder in your public_html folder and you upload the site content into that folder. So, essentially you are running 2 separate sites, separate content, off one account. The Basic plan and Business plan both come with unlimited addon domains included. This does not include domain registration. You may add it in cpanel under addon domains. New Domain Name: mynewdomain.com Username/directory/subdomain Name: name you want for the folder such as mynewdomain Password: Cpanel password Ignore any bind errors. If it is successful, you will see it in the addons list and there will be a new subdomain for it under Subdomains. Be sure to change the nameservers at your current registrar of domains you are adding or parking to the same nameservers as your primary domain is using. The nameservers are given in your Critical Account Info we sent on signup and as seen in your CAP panel. Changes take 24-72 hours to propagate.

Sub/Addon/Parked Domains

What is the difference between a subdomain, parked domain and add on domain?
*Subdomains:

A subdomain name points to a subfolder of the primary domain. For instance, cats.pets.com would point to a subfolder such as /cats under the primary domain of pets.com. Its content is separate from the main site so it can act like a separate site though usually it will have some relevance to the main site as you can see above.

A subdomain can also be used on our system to redirect to somewhere else and create a shorter way to get there. For instance, mymail.mydomain.com could be redirected to http://mydomain.com/webmail/horde/ to get to webmail easier and force the use of the Horde webmail client.

Unlimited subdomains come with each hosting account.

*Parked Domains (Aliases):

A parked domain is an additional domain that points to the main directory of your account. You can park unlimited domains at no cost on both the Basic and Business plans.

A parked domain will resolve to your primary domain name.

Say your primary is domain1.com and you park domain2.com. In the address bar if you type domain2.com it will resolve to domain1.com but in the address bar you will see domain2.com. This is a parked domain.

*Addon domains:

An add on domain allows you to run a separate web site to your primary domain. When you create an add on domain it makes a folder in your public_html folder and you upload the site content into that folder.

So, essentially you are running 2 separate sites, separate content, off one account.

The Basic plan and Business plan both come with unlimited addon domains included. This does not include domain registration.

You may add it in cpanel under addon domains.

New Domain Name: mynewdomain.com
Username/directory/subdomain Name: name you want for the folder such as mynewdomain
Password: Cpanel password

Ignore any bind errors. If it is successful, you will see it in the addons list and there will be a new subdomain for it under Subdomains.

Be sure to change the nameservers at your current registrar of domains you are adding or parking to the same nameservers as your primary domain is using. The nameservers are given in your Critical Account Info we sent on signup and as seen in your CAP panel. Changes take 24-72 hours to propagate.

P2P Telephony Explained

2008-07-28T21:07:00.001+10:00

http://www.skype.com/help/guides/p2pexplained/

P2P Telephony Explained — For Geeks Only

See also the Skype Technical FAQ for answer to specific questions.

Peer-to-peer ("P2P") technology was first widely deployed and popularized by file-sharing applications such as Napster and KaZaA. In this context, P2P technology allows users to share, search for and download files. The P2P term has been widely used and just as often abused. Companies both large and small, self-proclaimed "pundits" and others to trying to cash in on the "P2P buzz" use this term as long as it involves some direct communication between users or nodes. This description of P2P completely misses the point.

A true P2P system, in our opinion, is one where all nodes in a network join together dynamically to participate in traffic routing-, processing- and bandwidth intensive tasks that would otherwise be handled by central servers.

A true P2P application empowers small teams with good ideas to develop software and businesses that can successfully challenge those of large companies. True P2P, when applied to ripe markets, is disruptive technology.

Decentralized P2P networks have several advantages over traditional client-server networks. These networks scale indefinitely without increasing search time and without the need for costly centralized resources. They utilize the processing and networking power of the end-users machines since these resources always grow in direct proportion to the network itself. Each new node added to the network adds potential processing power and bandwidth to the network. Thus, by decentralizing resources, second generation (2G) P2P networks have been able to virtually eliminate costs associated with a large centralized infrastructure.

P2P telephony became a natural next step where P2P could have a significant disruptive impact and Skype was founded to develop the first P2P telephony network.

Internet-based telephony – Voice-over-IP – (VoIP) has been around for years but has not reached the mainstream market. The reasons for this are quite clear to those of us who have tried VoIP software:

Products which have a true cost-saving advantage over standard telephones do not have comparable quality.
Call-completion rates are very low due to firewalls and the use of Network Address Translation (which renders over 50% of residential computers unable to communicate with traditional VoIP software).
The User Interface is typically bloated and requires substantial configuration and technical skills.

Centralization can overcome some of these difficulties by routing calls through firewalls or NAT's. However, this brings the cost of running the network to levels approaching that of the existing telecom networks. In addition, these costs scale proportionally with the number of users. The result is that companies operating such services typically allocate very little resources on their servers per user which seriously degrades the call quality.

The Skype team has succeeded in leveraging all of the available resources in a network. This has allowed us to raise the call completion rate and quality in the Skype network to levels exceeding that of POTS ("Plain Old Telephony System"). This is all achieved without the need for costly centralized resources. In addition, we also believe that we have created the most user friendly interface around!

The following are some of the techniques that Skype employs to deliver state-of-the-art IP-based telephony.

Firewall and NAT (Network Address Translation) traversal.

Non-firewalled clients and clients on publicly routable IP addresses are able to help NAT'ed nodes to communicate by routing calls. This allows two clients who otherwise would not be able to communicate to speak with each other. Because the calls are encrypted end-to-end, proxies limit the security or privacy risk.

Likewise, only proxies with available spare resources are chosen so that the performance for these users is not affected.

Several new techniques were also developed in order to avoid end-user configuration of gateways and firewalls, whose non-intuitive configuration settings typically prohibit the majority of users from communicating successfully. In short, Skype works behind the majority of firewalls and gateways with no special configuration.

Global decentralized user directory.

Most instant message or communication software requires some form of centralized directory for the purposes of establishing a connection between end users in order to associate a static username and identity with an IP number that is likely to change. This change can occur when a user relocates or reconnects to a network with a dynamic IP address. Most Internet-based communication tools track users with a central directory which logs each username and IP number and keeps track of whether users are online or not. Central directories are extremely costly when the user base scales into the millions. By decentralizing this resource-hungry infrastructure, Skype is able to focus all of our resources on developing cutting-edge functionality.

P2P network technologies used by file-sharing applications would be almost suitable for decentralizing this, but those networks are fragmented in nature – a search does not reach all nodes in the network. Clearly, in order to deliver high quality telephony with the lowest possible costs, a third generation of P2P technology ("3G P2P"), or Global Index (GI) was a necessary development and represents yet another paradigm shift in the notion of scaleable networks. The Global Index technology is a multi-tiered network where supernodes communicate in such a way that every node in the network has full knowledge of all available users and resources with minimal latency.

Intelligent routing.

By using every possible resource, Skype is able to intelligently route encrypted calls through the most effective path possible. Skype even keeps multiple connection paths open and dynamically chooses the one that is best suited at the time. This has the noticeable effect of reducing latency and increasing call quality throughout the network.

Security.

Skype encrypts all calls and instant messages end-to-end for unrivaled privacy. Encryption was necessary since all calls are routed through the public Internet.

Super-simple UI.

We believe that software should work for you and not against you and so we have designed Skype to be dead-simple to use – people who can use Windows and telephones will feel at home with Skype immediately, and the software works equally well and is simple to use also on other platforms where Skype runs (Pocket PC, Linux, Mac OS X).

Fwd: [nbannounce] NetBeans IDE 6.0 Available

2007-12-05T10:56:00.000+10:00

---------- Forwarded message ----------
From: NetBeans Webmaster <webmaster@netbeans.org>
Date: Dec 5, 2007 7:52 AM
Subject: [nbannounce] NetBeans IDE 6.0 Available
To: nbannounce@netbeans.org

NetBeans.org is proud to announce the availability of NetBeans IDE 6.0.

The focus of NetBeans IDE 6.0 is superior developer productivity with a smarter, faster editor, and the integration of all
NetBeans products into one IDE. NetBeans IDE 6.0 features Ruby/JRuby/Ruby on Rails support, enhancements for
improved Swing development, a new Visual Game Designer, updated Data Binding support, integrated Profiling, and more.
The new installer lets you customize your download preferences--use it to choose the features and runtimes you need.
Highlights of NetBeans IDE 6.0 are:

Java
* Swing GUI Builder
* Intelligent Editor
* Profiler
* Debugger
* Updated Platform APIs

C/C++
* C/C++ Projects and Templates
* Source Code Editor
* Multiple Configurations
* Class Hierarchy Browser
* File Navigation

Ruby
* Ruby on Rails Support
* JRuby Runtime
* Code Completion
* Debugger
* Refactoring

Mobility
* Game Builder
* Device Fragmentation
* SVG Graphics
* Web Services
* Handheld Device / Set Top Box

Web & Java EE
* Visual JSF Design
* Enhanced JavaScript
* AJAX Enabled Components
* CSS Editor
* Web Services & SOA

SOA
* XML Schema Editor, XSLT Designer
* WSDL Designer
* BPEL Designer
* Service Assembly Editor
* Deploy to JBI compliant runtime

You have received this email because you are subscribed to the nbannounce mailing list from NetBeans.org. If you do not wish to receive this newsletter, you can unsubscribe here.

--
Zhipeng Zhang (Alan) BCompSc MInfoTech MACS(Prov)

"You must be the change you wish to see in the world."

"Begin at the beginning and go on till you come to the end; then stop."
-- Lewis Carroll, Alice in Wonderland

My Photo Albums on zhipeng-zhang.com

2007-09-28T00:35:00.001+10:00

zhipeng-zhang.com/plogger/ (most adorable)

What's New in Version 3.0?

Build your Own Themes — Use Plogger's simple template based theme system to create your own custom skins. If you are saavy, you can even integrate your own Javascript effects. Switch themes with the click of a button! Three themes are included in the package.
Plogger XML Service — Each Plogger gallery now has a full XML generator built-in. Create your own widgets in any language you choose, whether it be a native desktop widget or a Javascript snippet.
Better International Support — Plogger now supports internationalization of the admin area through the GetText framework and will be available in many languages. Plogger also now supports better usage of the UTF-8 Character set in the storage engine.
AJAX inline-editing — You can now edit descriptions and captions for any picture on-the-fly with our slick AJAX inline editors.
Include from Anywhere — Now you can include Plogger from any directory or page on your website
Upload Zip Files — Upload a zip file full of pictures and Plogger will automatically unpack and import them to your gallery
Description fields for pictures — All your images can now have captions and descriptions if you'd like
Tons of Bug Fixes — Version 3.0 is a complete rewrite of version 2.0. We now have definable sort orders, SEO friendly page titles, better large file support, a brand new user interface, and tons of bug fixes!

http://zhipeng-zhang.com/CopperminePG/index.php

(excellent, same as plogger, but with community functions, users can have, upload their own album)

.:: Entry

01: Welcome to Coppermine Photo Gallery's homepage!

Coppermine is a multi-purpose fully-featured and integrated web picture gallery script written in PHP using GD or ImageMagick as image library with a MySQL backend.

Coppermine is free software which you can download and install on your webspace. If you came here from a "Powered by Coppermine" link on a photo gallery, please read these Frequently-Asked Questions.

The default CPG theme's front page.

.:: Requirements

02: Web Server + PHP + MySQL + IM/GD = CPG!

Coppermine Photo Gallery has been tested working well on IIS, Apache 1.3.24 onwards to the latest Apache 2, on Linux, UNIX, OSX, and Win32 systems. The following settings are required:

Good webserver (Apache recommended);
PHP (4.1.0 or better);
MySQL (3.23.23 or better; 4.x recommended);
either GD or ImageMagick (any version);

.:: Current features

03: Endless Features!

CPG is so fully featured it's not enough to fully list them here. Feel free to have a go with the demo - change the themes, add some comments, see it in Hungarian!

arrangement of pictures in categories and albums;
picture information stored in database;
users can upload pictures with web interface of ftp (and admin can batch-add to database);
full multimedia support
creation of thumbnails and intermediate size pics;
search feature;
last added;
random picture;
user management (private galleries, groups);
integration of user management with various bbs (like phpBB, YaBB SE, SMF, Invisionboard, vbulletin);
caption, title, description and user defined fields for each picture (searchable);
easy install (installer provided);
multi-lingual: Arabian, Brazilian Portuguese, Bulgarian, Catalan, Chinese (both Big-5 and GB), Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German (both "Du" and "Sie"), Greek, Hebrew, Hungarian, Indonesian, Italian, Japanese, Latvian, Malay, Norwegian, Polish, Romanian (both with and without diacritics), Russian, Slovenian, Spanish, Swedish, Uighur, Vietnamese; if your language is not on the list, you can easily create a translation for your own language;
user comments;
e-card feature;
slideshow viewer;
all features customizable with web interface (admin section);
template system;
user membership in multiple groups;
upload approval notice for admin;
EXIF/IPTC support;
language selection option in template;
image rotation;
multi-pic upload;
separation of the breadcrumb block so that it can be placed independently of category in the template;
option to choose max height or width for thumbnails will help in creating nicer looking thumbnail rows and cols;
option to display a clickable flimstrip of thumbnails below the image display;
option to show first level albums of a category instead of just statistics of the category;
option of turning on OR off the showing of "Private" Icon to unlogged / unprivileged user;
title option to sort in albums;
online help feature for the admin pages;
plugin-API;
English as a fallback language for un-translated entries in language files;
password-protected albums;
more admin-settable user profile fields;
picture-resize on upload;
bbs integration settable with a wizard-like user interface;
advanced search (boolean operators);

Customise your frontpage through CSS, PHP or plain HTML!

Unlimited multiple albums and categories using MySQL.

Film strip for that easy access.

.:: Future plans

04: What does the near future hold?

The developers are excited about releasing a new version which may include the following features (check out the forum):

integration of various hacks/user contributions into the release package;
advanced e-card feature (plain-text mails);
template-building tutorial;
optional dhtml navigation;
Permanent URLs for search engine friendliness (using PID instead of POS)
Rating on thumbnails page
Registration disclaimer optional
From thumbnail to Pop-Up option
Coppermine API
Comment approval
Comment and registration captcha class
Global password for registration
Watermarking
Thumb cropping and sharpening
Movie download option
Ecard flash support
Random album thumbnail
Tag cloud for keywords
Moderator for album pictures

zhipeng-zhang.com/phpalbum/ (simple and powerful, allow comments, ecard)

PHP Photo Album / Gallery

Very userful and handy. E-Card on pictures.

PHP Photo Album / Gallery

Submitted by patrik on Wed, 2005-12-21 10:19.

phpAlbum.net is an Open Source PHP script which allows you to create your personal Photo Album / Gallery in just a seconds. All you need is a web space with FTP access. No database is needed. After a few clicks with our phpAlubm.net Installer you are ready to upload your photos, create new directories /galleries, and use your photo album.

These are the features which phpAlbum.net offers you:

Automatic generation of thumbnails and resized
Commenting of pictures with antispam security code
NEW! IPTC Support, import of keywords and picture description, showing other IPTC-tags
NEW! E-Card - you can now send e-cards to your friends and family
Screenshots for files to be downloaded, movie, audio, exe or whatever
Password protection for your private galleries
Admin section for creating new directories, uploading photos (works even with PHP safe_mode=on),Uploading ZIP Files preserving directory structure
Short and long description of galleries/directories and photos
Highly customizable layout, separated layout(HTML) from functional code, this allows easy creation of new themes
Caching of all generated thumbnails and resized photos
Transparent logo and icon processing with any background color, including IE6
Access logging, with exclude strings
And last but not least, you can help us with your suggestions to create usable, easy to install, php photo album script.

zhipeng-zhang.com/TinyWebGallery/ (customisable album, mp3, avi, flv, etc could be displayed in the built in program)

TinyWebGallery Overview

The TinyWebGallery is a free php based gallery that is very easy to install, extremely user friendly, does not need a database (uses xml files) but still has all the features you should expect and much more.
Besides the features you find in most other galleries TWG has e.g.

AJAX navigation with sliding thumbnails
xml based comments/captions/view counter/Top X/Rating
with security image ...
TWG Admin to upload/manage images, manage users,
Color Manager, Configuration of TWG ...
Keyboard navigation (arrow keys)
3 different slideshow types
Protected galleries,
Text and image watermarks
Embeded video support (new 1.5)
TWG Flash uploader (new 1.5)
Tag support (new 1.6)
Frontend is available in 23, backend in 4 languages! (new 1.6)
Supports all file formats like avi, mpg, mp3 for download
Fullscreen mode
Remote picture support
Low bandwith mode for slow connections
Can be integrated or integrates existing html e.g. as footer, header or
inside the page
All features can be enabled/disabled/configured
And a lot of small things that makes this gallery unique right now.

TWG can be configured very fast for a professional gallery like a model agency but also for the pictures from the last ski holiday! Just check out the demos and the list of all functions. Maybe TWG is the image gallery you where looking for so long!

zhipeng-zhang.com/psipuss/ (simple photo album, allow users to upload pics, good for friends who need album space)

front end users can upload iamges and manage their own downloaed images.

psi-labs.com FREE Photo Uploader Share Script

A Photo / Images upload script created in php mysql, it allows members to upload images, photos to your website.

psi-labs.com photo upload share script

psipuss version 1.0 Released 14.04.07

To login to admin

http://www.hotscreenplay.com/photo/admin/
username: admin
password: 123

To login as a user

http://www.hotscreenplay.com/photo/

psipuss is free under the gnu license

Download Now in rar
Download Now in zip

php mysql script to share images

To remove our powered buy link at the bottom of the script: its only $10 per domain so please paypal $10 per domain name to sales at psi-labs.com include the domain name in the paypal payment. or email us for other payment options.

Join the mailing list for the cool new updates and scripts.

Photo gallery, Images upload script, upload images, pics, jpg, gif, bpm, photos.

psi photo upload share script

Allows members to upload images to your website

zhipeng-zhang.com/weatimages/

much alike the Plogger, less functionality. simple and good.

zhipeng-zhang.com/imagegallery/

lightbox driven gallery. ECard.

zhipeng-zhang.com/MicroPhoto/

only two progam files needed. The images on the home directory and display straight away. Not powerful. Good for small amount of pic demo.

Translating_WordPress Procedure

2007-09-27T15:10:00.001+10:00

http://codex.wordpress.org/Translating_WordPress

Table of contents [ showhide]

1 Translating WordPress

1.1 Qualifications
1.2 About Locales

2 Localization Technology

2.1 gettext files

3 Translation Tools

3.1 Translating With Launchpad
3.2 Translating With poEdit
3.3 Translating With KBabel
3.4 Translating With Gettext Tools

3.4.1 The PO File Header
3.4.2 Message Format

4 Types of messages

4.1 Labels

4.1.1 Examples

4.2 Informational Messages

4.2.1 Examples

4.3 Date and Time Locale Settings

4.3.1 Month names
4.3.2 Month abbreviations
4.3.3 Weekday Names
4.3.4 Weekday Abbreviations
4.3.5 Weekday Initials
4.3.6 Date Formatting Strings
4.3.7 Translation via WordPress-PHP

4.4 Messages With Placeholders

4.4.1 Examples

5 Tips for Good Translations

6 WordPress Localization Repository

6.1 Participating
6.2 Guidelines and requirements

6.2.1 Character Encodings
6.2.2 HTML Character Entities
6.2.3 Repository File Structure

7 Troubleshooting

8 Resourcess

Internationalization and localization are terms used to describe the effort to make WordPress (and other such projects) available in languages other than English, for people from different locales, who use different dialects and local preferences.

The process of localizing a program has two steps. The first step is when the program's developers provide a mechanism and method for the eventual translation of the program and its interface to suit local preferences and languages for users worldwide. WordPress developers have done this, so in theory, WordPress can be used in any language.

The second step is the actual localization, the process by which the text on the page and other settings are translated and adapted to another language and culture, using the framework prescribed by the developers of the software. WordPress has already been localized into many other languages (see WordPress in Your Language for more information).

This article explains how translators (bi- or multi-lingual WordPress users) can go about localizing WordPress to more languages.

[ edit ]

Translating WordPress

Before you start translating WordPress, check WordPress in Your Language (and resources cited there) to see if a translation of WordPress into your language already exists. It is also possible that someone (or a team) is already working on translating WordPress into your language, but they haven't finished yet. To find out, subscribe to the wp-polyglots mailing list , introduce yourself, and ask if there's anyone translating into your language. There is also a list of localization teams and localization teams currently forming, which you can check to see if a translation is in progress.

[ edit ]

Qualifications

Assuming that a WordPress translation into your language does not already exist or have someone working on it, you may want to volunteer to create a public translation of WordPress into your language. If so, here are the qualifications you will need:

You need to be truly bilingual -- fluent in both written English and the language(s) you will be translating into. Casual knowledge of either one will make translating difficult for you, or make the localization you create confusing to native speakers.
You need to be familiar with PHP, as you will sometimes need to read through the WordPress code to figure out the best way to translate messages.
You should be familiar with human language constructs: nouns, verbs, articles, etc., different types of each, and be able to identify variations of their contexts in English.

[ edit ]

About Locales

A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil).

You can do a translation for any locale you wish, even other English locales such as Canadian English or Australian English, to adjust for regional spelling and idioms.

The default locale of WordPress is U.S. English.

[ edit ]

Localization Technology

WordPress's developers chose to use the GNU gettext (http://www.gnu.org/software/gettext/gettext.html ) localization framework to provide localization infrastructure to WordPress. gettext is a mature, widely used framework for modular translation of software, and is the de facto standard for localization in the open source/free software realm.

gettext uses message-level translation — that is, every "message" displayed to users is translated individually, whether it be a paragraph or a single word. In WordPress, such "messages" are generated, translated, and used by the WordPress PHP files via two PHP functions. __() is used when the message is passed as an argument to another function; _e() is used to write the message directly to the page. More detail on these two functions:

__($message): Searches the localization module for the translation of $message, and passes the translation to the PHP return statement. If no translation is found for $message, it just returns $message .
_e($message): Searches the localization module for the translation of $message, and passes the translation to the PHP echo statement. If no translation is found for $message, it just echoes $message .

Note that if you are internationalizing a Theme or Plugin, you should use a "Text Domain". See Writing a Plugin for more information on how to do this for a plugin; themes are similar.

The gettext framework takes care of most of WordPress. However, there are a few places in the WordPress distribution where gettext cannot be used -- see Files For Direct Translation for more information on how to translate these spots.

[ edit ]

gettext files

There are three types of files used in the gettext translation framework. These files are used and/or generated by translation tools during the translation process, as follows:

POT (Portable Object Template) files: The first step in the localization process is that a program is used to search through the WordPress source code and pick out every message passed into a __() or _e() function. This list of English-language messages is put into a specially-formatted template file (POT file) that forms the basis of all translations. Generally, you can download a POT file for WordPress, so you shouldn't have to generate your own. Separate POT files can also be made for themes and plugins, if the theme/plugin developer has enclosed all text in __() or _e() functions.

PO (Portable Object) files: The second step in the localization process is that the translator translates all the messages from the POT file into the target language, and saves both English and translated messages in a PO file.

MO (Machine Object) files: The final step in the localization process is that the PO file is run through a program that turns it into an optimized machine-readable binary file (MO file). Compiling the translations to machine code makes the localized program much faster in retrieving the translations while it is running.

[ edit ]

Translation Tools

There are various tools available to aid in translating. You may use whichever you prefer.

Launchpad ( https://translations.launchpad.net/): The Ubuntu Linux project has a web site that allows you to translate messages without even looking at a PO or POT file, and export directly to a MO.

Note: many translators have found Rosetta to be a good starting point, but once it comes time to proofread the entire list of translations, many have opted to switch hand-editing the PO file or using a program like poEdit or KBabel, since the Rosetta UI lacks a search feature and other things that become essential when proofreading and editing.

poEdit ( http://www.poedit.net/ ): An open source program for Windows, Mac OS X and UNIX/Linux which provides an easy-to-use GUI for editing PO files and generate MO files.

KBabel ( http://i18n.kde.org/tools/kbabel/): Another open source PO editing program for the KDE window manager on Linux.

GNU Gettext ( http://www.gnu.org/software/gettext/): The official Gettext tools package contains command-line tools for creating POTs, manipulating POs, and generating MOs. For those comfortable with a command shell.

[ edit ]

Translating With Launchpad

Go to Launchpad's WordPress translation page (https://launchpad.net/wordpress/2.1/+pots/wordpress ).
If you're not already logged in to Launchpad, choose "Log In / Register" at the top right. Log in, or create a Launchpad account if you don't have one already.
Choose a language to begin translating.

When you are finished with your translation, you can export it as a PO or MO file if you like, by visiting the PO File Details page for your language and clicking on Export as PO file or Export as MO file .

[ edit ]

Translating With poEdit

Download and install poEdit ( http://www.poedit.net/)
Download the official WordPress POT file ( http://svn.automattic.com/wordpress-i18n/pot/trunk/wordpress.pot)

The poEdit screen
Open the file in poEdit.
(See Image) The box labeled (1) is the original message (in English) from the POT file. The box labeled (2) is where you add your translation. Boxes labeled (3) and (4) are used for adding comments about the messages. These come in handy if you are working with a team of translators and would like to pass around ideas through the PO file.
Go to File → Save as… to save your translations in a PO file.
When you are finished translating, go to File → Save as… again to generate the MO file.
Or you can set your poEdit to always compile a MO file when saving changes by clicking File → Preferences and on the Editor tab check the Automatically compile .mo file on save box.

[ edit ]

Translating With KBabel

This section is incomplete.

Download the official WordPress POT file ( http://svn.automattic.com/wordpress-i18n/pot/trunk/wordpress.pot)
Open the file in KBabel

[ edit ]

Translating With Gettext Tools

Download the official WordPress POT file ( http://svn.automattic.com/wordpress-i18n/pot/trunk/wordpress.pot)
Open the file in your favorite text editor
Update the header information
Translate the messages
Save the file with a .po file extension
Issue msgfmt -o filename.mo filename.po

[ edit ]

The PO File Header

At the beginning of the PO file is something called the header. This gives information about what package and version the translation is for, who the translator was, and when it was created. Certain portions of this header should be universal for all WordPress translations:

# LANGUAGE (LOCALE) translation for WordPress. # Copyright (C) YEAR WordPress contributors. # This file is distributed under the same license as the WordPress package. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: WordPress VERSION\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2005-02-27 17:11-0600\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n"

Fill in the rest of the capitalized text with the appropriate values.

[ edit ]

Message Format

The remainder of the file will be in a format as follows:

#: wp-comments-post.php:13 msgid "Sorry, comments are closed for this item." msgstr ""  #: wp-comments-post.php:29 msgid "Sorry, you must be logged in to post a comment." msgstr ""  #: wp-comments-post.php:35 msgid "Error: please fill the required fields (name, email)." msgstr ""

The first line of each message contains the location of the message in the WordPress code. In the case of these messages, they're all located in wp-comments-post.php, on lines 13, 29, and 35, respectively. Occasionally you will come across a message for which you will need to check its context; look at the appropriate line or lines in the WordPress core, and you should be able to figure out when and where the message is displayed, and even reproduce it yourself using your web browser. Some messages will also appear with the same text in multiple locations; in that case, there may be more than one line giving a file and line location.

The next line, msgid, is the source message. This is the string that WordPress passes to its __() or _e() functions, and the message you will need to translate.

The final line, msgstr, is a blank string where you will fill in your translation.

Here's how the same few lines would look after being translated, using the French (France) (http://svn.automattic.com/wordpress-i18n/fr_FR/trunk/messages/fr_FR.po ) locale as an example:

#: wp-comments-post.php:13 msgid "Sorry, comments are closed for this item." msgstr "L'ajout de commentaire n'est pas ou plus possible pour cet article."  #: wp-comments-post.php:29 msgid "Sorry, you must be logged in to post a comment." msgstr "Vous devez être connecté pour rédiger un commentaire."  #: wp-comments-post.php:35 msgid "Error: please fill the required fields (name, email)." msgstr "Erreur : veuillez remplir les champs obligatoires vides (nom, e-mail)."

Note: see Character encodings and HTML character entities below for notes on when to use HTML character entities in translation.

[ edit ]

Types of messages

[ edit ]

Labels

Labels are often used in the context of HTML <label>, <legend>, <a>, or <select> tags. They are short and precise descriptors of the purpose of a UI element. These can be very difficult to translate at times, especially if they are single words, and if the word used in English can be interpreted as either a noun or imperative verb. With most labels you will need to do some searching through the code to find the context of its use before coming up with an appropriate translation.

Because so many of the messages are part of the WordPress administration interface, Labels are probably the most frequent type of message to translate.

[ edit ]

Examples

msgid "Post" msgstr "Artikkeli"

"Post" could be interpreted as an imperative verb, but in this context it's a noun. The noun form of "post" in English can be difficult to translate, and the most appropriate translation has been difficult for some teams to decide upon. Many translations use their language's equivalent to the English "Article," as this one does. (From the Finnish (Finland) (http://svn.automattic.com/wordpress-i18n/fi_FI/trunk/messages/fi_FI.po ) translation.)

#: wp-login.php:79 wp-login.php:233 wp-register.php:166 #: wp-includes/template-functions-general.php:46 msgid "Register" msgstr "रजिस्टर"

From the Hindi translation.

#: wp-admin/admin-functions.php:357 msgid "- Select -" msgstr " - Dewis -"

Items like the surrounding dashes in this example can be eliminated or replaced if they might be confusing to users in your target locale, or if there are different established conventions for your locale. From the Welsh translation.

[ edit ]

Informational Messages

Another frequent type of message, the informational message is usually composed of full sentences, and conveys information or requests an action of the user. Since these tend to be longer than labels, they tend to be slightly easier to translate. However, with the longer messages comes more variation in the level of formality (or informality), which is something translators need to be aware of.

[ edit ]

Examples

#: wp-login.php:146 msgid "Your new password is in the mail." msgstr "Вашата нова парола е в електронната ви поща."

This particular message contains a modified English formulaic expression ("the check/cheque is in the mail"), which contributes to its informality. (From the Bulgarian (Bulgaria) (http://svn.automattic.com/wordpress-i18n/bg_BG/trunk/messages/bg_BG.po ) translation.)

#: wp-includes/functions.php:1636 msgid "<strong>Error</strong>: Incorrect password." msgstr "<strong>FEL</strong>: Felaktigt lösenord."

Error messages tend to be more formal, simply because they're short and concise. (From the Swedish (Sweden) (http://svn.automattic.com/wordpress-i18n/sv_SE/trunk/messages/sv_SE.po ) translation.)

#: wp-includes/functions-post.php:467 msgid "Sorry, you can only post a new comment once every 15 seconds. Slow down cowboy." msgstr "Leider kannst du nur alle 15 Sekunden einen neuen Kommentar eingeben. Immer locker bleiben."

Of course, not all of them. (From the German (Germany) (http://svn.automattic.com/wordpress-i18n/de_DE/trunk/messages/de_DE.po ) translation.)

[ edit ]

Date and Time Locale Settings

Rather than using PHP's built-in locale switching features, which is not configured for very many languages on most hosts, WordPress uses the gettext translation module to accomplish date and time translations and formatting.

WordPress translates the following:

[ edit ]

Month names

#: wp-includes/locale.php:42 wp-includes/locale.php:57 msgid "May" msgstr "Květen"

(From the Czech (Czech Republic) (http://svn.automattic.com/wordpress-i18n/cs_CZ/trunk/messages/cs_CZ.po ) translation.)

[ edit ]

Month abbreviations

#: wp-includes/locale.php:57 msgid "May_May_abbreviation" msgstr "Mag"

Note the unusual msgid. These messages should NOT be translated literally: they are a hack to get around the fact that in English, the full name and abbreviation for May are the same, which Gettext would erroneously combine into one entry. (From the Italian (Italy) (http://svn.automattic.com/wordpress-i18n/it_IT/trunk/messages/it_IT.po ) translation.)

[ edit ]

Weekday Names

#: wp-includes/locale.php:7 #: wp-includes/locale.php:18 #: wp-includes/locale.php:31 msgid "Tuesday" msgstr "火曜日"

(From the Japanese (Japan) (http://svn.automattic.com/wordpress-i18n/ja_JP/trunk/messages/ja_JP.po ) translation.)

[ edit ]

Weekday Abbreviations

#: wp-includes/locale.php:31 msgid "Tue" msgstr "Уто"

(From the Serbian (Serbia & Montenegro) (Cyrillic) ( http://svn.automattic.com/wordpress-i18n/sr_CS/trunk/messages/sr_CS.po ) translation.)

[ edit ]

Weekday Initials

#: wp-includes/locale.php:18 msgid "T_Tuesday_initial" msgstr "ti"

The weekday initials are for WordPress's calendar feature, and use the same hack as the month abbreviations to get around the fact that in English Tuesday and Thursday share the same first letter. Not all locales use single-letter abbreviations for all days: in this example, Norwegian Bokmål uses an extra letter to distinguish tirsdag (Tuesday) and torsdag (Thursday). (From the Norwegian Bokmål (Norway) ( http://svn.automattic.com/wordpress-i18n/nb_NO/trunk/messages/nb_NO.po ) translation.)

[ edit ]

Date Formatting Strings

These are PHP date() ( http://php.net/date ) formatting strings, and they allow you to change the formatting of the date and time for your locale.

WordPress uses the translations elsewhere in the localization file for month names, weekday names, etc. This special string is for the selection of which elements to include in the date & time, as well as the order in which they're presented.

Take this msgid from the theme.pot file:

#: archive.php:40 search.php:19 single.php:22 msgid "l, F jS, Y" msgstr ""

In English, this gets formatted as:

Sunday, February 27th, 2005

However, different locales format their dates differently. In Danish, for example, dates are written:

søndag, 27. februar 2005

To accomplish this, the msgid above would be translated to:

#: archive.php:40 search.php:19 single.php:22 msgid "l, F jS, Y" msgstr "l, j. F Y"

To use another example, one way to format dates in Chinese and Japanese is as follows:

2005年2月27日

This would be accomplished in the translation like this:

#: archive.php:40 search.php:19 single.php:22 msgid "l, F jS, Y" msgstr "Y年n月j日"

Lastly, if you need to include literal alphabetic characters in your date format, as sometimes occurs in Spanish, you can backslash them:

#: archive.php:40 search.php:19 single.php:22 msgid "l, F jS, Y" msgstr "l j \d\e F \d\e Y "

This would output:

domingo 27 de febrero de 2005

[ edit ]

Translation via WordPress-PHP

To translate your Date e.g. inside your plugin use the wp-function mysql2date(Dateformat, Datestring) ( http://code.wordpress.de/xref/nav.htm?wp-includes/functions.php.htm#mysql2date ). It uses the month- and week-translations to return your date.

[ edit ]

Messages With Placeholders

Many messages contain special PHP formatting placeholders, which allow the insertion of untranslatable dynamic content into the message after it is translated. The PHP placeholders come in two different formats:

%s: When only one placeholder is present, this marker is used.
%1$s, %2$s, %3$s, …: Numbered placeholders, which allow translations to rearrange the order of the placeholders in the string while maintaining the information each is replaced with.

[ edit ]

Examples

#: wp-login.php:116 msgid "The e-mail was sent successfully to %s's e-mail address." msgstr "El e-mail fue enviado satisfactoriamente a la dirección e-mail de %s"

This message inserts the username of the user to which an email has been sent. (From the Spanish (Spain) (http://svn.automattic.com/wordpress-i18n/es_ES/trunk/messages/es_ES.po ) translation.)

#: wp-admin/upload.php:96 #, php-format msgid "File %1$s of type %2$s is not allowed." msgstr "类型为%2$s的文件%1$s不允许被上传。"

This message reverses the order in which the file name and type are used in the translation. (From the Chinese (China) (http://svn.automattic.com/wordpress-i18n/zh_CN/trunk/messages/zh_CN.po ) translation.)

[ edit ]

Tips for Good Translations

Don't translate literally, translate organically: Being bi- or multi-lingual, you undoubtedly know that the languages you speak have different structures, rhythms, tones, and inflections. Translated messages don't need to be structured the same way as the English ones: take the ideas that are presented and come up with a message that expresses the same thing in a natural way for the target language. It's the difference between creating an equal message and an equivalent message: don't replicate, replace. Even with more structural items in messages, you have creative license to adapt and change if you feel it will be more logical for, or better adapted to, your target audience.

Try to keep the same level of formality (or informality): Each message has a different level of formality or informality. Exactly what level of formality or informality to use for each message in your target language is something you'll have to figure out on your own (or with your team), but WordPress messages ( informational messages in particular) tend to have a politely informal tone in English. Try to accomplish the equivalent in the target language, within your cultural context.

Don't use slang or audience-specific terms: Some amount of terminology is to be expected in a blog, but refrain from using colloquialisms that only the "in" crowd will get. If the uninitiated blogger were to install WordPress in your language, would they know what the term means? Words like pingback, trackback, and feed are exceptions to this rule; they're terminology that are typically difficult to translate, and many translators choose to leave in English.

Read other software's localizations in your language: If you get stuck or need direction, try reading through the translations of other popular software tools to get a feel for what terms are commonly used, how formality is addressed, etc. Of course, WordPress has its own tone and feel, so keep that in mind when you're reading other localizations, but feel free to dig up UI terms and the like to maintain consistency with other software in your language.

[ edit ]

WordPress Localization Repository

The WordPress Localization Repository at http://svn.automattic.com/wordpress-i18n/ is a Subversion repository where official WordPress translations are maintained. Various teams collaborate on translations for their native language, and team maintainers commit updates and changes to the repository.

[ edit ]

Participating

Participation in the repository is open to anyone. Simply subscribe to the wp-polyglots mailing list , introduce yourself, and let everyone know what translation you'd like to work on. If there is already a team for your language and locale, they'll let you know and you can join them. If not, you can either volunteer to be a maintainer for your language and locale, or simply contribute your localization and the repository maintainers will add it.

[ edit ]

Guidelines and requirements

Note: these guidelines are subject to change as the system evolves; repository maintainers will be happy to assist you in updating the files you maintain in the repository should these guidelines change.

[ edit ]

Character Encodings

All localizations should have at least a UTF-8 version, but may optionally add versions in other character encodings popular for that locale.

PHP does not support Byte Order Markers (BOMs), so be sure the UTF-8 encoded files you contribute do not have them.

[ edit ]

HTML Character Entities

With a few exceptions (noted below), all translations should be written literally, rather than escaping accented and special characters with HTML character entities.

Some characters must be escaped to avoid conflict with XHTML markup: angle brackets (< and >), and ampersands (&). In addition, there are a few other characters better used escaped, such as non-breaking spaces (  ), angle quotes (« and »), curly apostrophes (’) and curly quotes.

For more information about the W3C's best practices involving character encodings and character entities, see the following references:

[ edit ]

Repository File Structure

The repository contains directories for each locale, which are named as follows:

ISO 639 language code ( http://en.wikipedia.org/wiki/ISO_639) (lowercase)
an underscore
ISO 3166-1 alpha-2 country code (http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) (uppercase)
If the directory is a variation in script for the same locale, an @ sign, plus the ISO 15924 script code (http://www.unicode.org/iso15924/iso15924-codes.html ).

Within each locale's directory are the regular Subversion versioning directories: branches/, tags/, and trunk/.

Inside the appropriate versioning directory are the following subdirectories:

dist/

This directory contains all files in the WordPress distribution that cannot be Gettexted, which have been translated into the target locale.

If the locale has only a UTF-8 translation of the files, the dist/ directory may be populated with them directly, and the structure within dist should mirror the structure of the wordpress root directory:

dist/
- license.html
- readme.html
- wp-config-sample.php
- …
- wp-admin/
  - install.php
  - upgrade.php
  - …

If the locale contains more than just a UTF-8 character encoding, then dist/ should contain subdirectories for each encoding:

dist/
- UTF-8/
  - license.html
  - readme.html
  - wp-config-sample.php
  - …
  - wp-admin/
    - install.php
    - upgrade.php
    - …
- ISO-8859-1/
  - …
- …

messages/

This directory contains the Gettext MO and PO files for the locale. Message files are named as follows:

ISO 639 language code ( http://en.wikipedia.org/wiki/ISO_639) (lowercase)
an underscore
ISO 3166-1 alpha-2 country code (http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) (uppercase)
a period
IANA character set name (http://www.iana.org/assignments/character-sets) , if other than UTF-8
a period, if character encoding name was specified
file extension (lowercase)

Examples:

cs_CZ.po        # UTF-8 character encoding ja_JP.EUC-JP.mo # EUC-JP character

theme/

Similarly to the dist/ dir, theme/ contains hard-translated theme files. If only a UTF-8 translation is present, the directory can be populated with subdirectories for each theme translated. These subdirectories contain all of the same files as the original theme (except that they're translated), and are named the same as the original theme:

theme/
- default/
  - 404.php
  - index.php
  - sidebar.php
  - …
  - images/
    - …

Just as with the dist/ directory, if there are multiple character encodings represented, theme/ should contain a subdirectory for each character encoding, which in turn would contain subdirectories for each theme translated.

[ edit ]

Troubleshooting

Rosetta won't export my translation as an MO file. It just says, "A system error occurred.": There is a syntax error in your translation that is preventing it from compiling to an MO. Download the PO instead and try compiling it manually with msgfmt. This will tell you which lines the errors are on so you can correct them by hand. If you don't have the GNU Gettext package installed, you can try opening the PO file in poEdit or KBabel to see if they will help you correct the errors, or you can email the wp-polyglots mailing list and ask for someone to debug it for you.

[ edit ]

Resourcess

Ryan Boren's Localizing Plugins and Themes ( http://boren.nu/archives/2004/11/01/localizing-plugins-and-themes/)

Retrieved from "http://codex.wordpress.org/Translating_WordPress "

Categories: Translating WordPress | Advanced Topics | WordPress Development

phpsitemapng

2007-09-25T14:37:00.001+10:00

http://enarion.net/google/phpsitemapng/

Installation of Google Sitemap generator phpSitemapNG

Download the current release and store it on your harddisc
Create a directory on your webserver (suggestion: /admin/phpsitemapng) and protect it
Extract this archive and copy the files to this directory on your website, copy sitemap.xml and sitemap.xml.gz into the root directory of your website.
Make the following files writable (chmod 0666):
- /sitemap.xml (- or /sitemap.xml.gz for compressed sitemap)
- /sitemap.txt (if you would like to write txt sitemaps files)
- settings/settings.inc.php (to store your settings)
- settings/files.inc.php - (store information about generated sitemap; only useful for small websites)
That's it, you can proceed with the usage of phpSitemapNG

Foreign languages / translations:

Deutsch - Hybrid GmbH

Next step: usage of phpSitemapNG

Usage of phpSitemapNG

http://enarion.net/google/phpsitemapng/usage/

Usage of Google Sitemaps generator phpSitemapNG - in English

Make shure you have installed this script as written at the phpSitemapNG installation guide

Follow theses steps to generate your sitemap:

1. Setup phpSitemapNG
2. Run phpSitemapNG
3. Edit the result
4. Store sitemap
5. Inform Google
6. Watch your website within Google

1. Setup phpSitemapNG

execute the script with your browser: browse to http://www.yourhost.com/admin/phpSitemapNG/ (take care of the capital letters).
You'll get a screen like this:

Set the settings according to the folling cases
Common settings:

Check the settings in Page root (this is the path on the webserver where your files are stored) and the Website (the url of your website) and maybe correct them if necessary.
Exclude directories - this directories will not be scanned for urls;
Example: to exlude all files in the directory img but not images, add /img/ to the list of directories; there is only a substring comparison performed
Exclude files - urls containing strings that are in this list, will neither be added to the sitemap nor crawled for urls

Please choose the item that matches your website and set the settings accordingly:

I am running a small website with less than 500 files

Make the following settings:

Check Ping google
Uncheck compress sitemap
Check Local file system scan and Scan website
Check Display edit screen after scan
Check Store filelist
Adapt Lastmod, Priority and Changefreq to your needs

With this settings, phpSitemapNG will scan your filesystem and crawl your website and finally give you an edit screen where you can adapt the values.

I am running a big website with more than 500 files

Make the following settings:

Check Ping google
Check compress sitemap
Check Local file system scan and maybe Scan website
Uncheck Display edit screen after scan
Uncheck Store filelist
Adapt Lastmod, Priority and Changefreq to your needs

With this settings, phpSitemapNG will scan your filesystem and maybe crawl your website and will write the result direct into the sitemap file.
There will be no edit screen since this can slow down or kill your browser. The created sitemap file will be compressed (if available). Check the expert settings to get some background information about the timeout functionality and the crawler if you're running into problems when saving the settings and executing the scan.

I am an expert and would like to know everything about phpSitemapNG

Ping google - inform Google when a sitemap has been created
Timeout functionality - phpSitemapNG allows you to set the time how long it will perform the actions. This is necessary if you're running a big website with many urls, but your webhoster allows you to execute php scripts only for a short amount of time.
There are two different timeouts that might occur:
1. PHP timeout: The PHP engine stops the exection and prints an error at the end of the script.
  Solution: Just press the Setup link, enable the timeout and type in the average time to the timeout (normally 30 seconds) minus 5 seconds (backup) time. :) Now the browser is forced to reload the page with javascript (if not enabled, please do it here!) when a timeout occurs.
2. Webserver timeout: The webserver stops the output thread and does not print an error at the end of the script.
  Solution: Just press the Setup link, enable the timeout and type in the average time to the timeout (normally 300 seconds) minus 5 seconds (backup) time. :)

2. Run phpSitemapNG

Press the Submit Settings button to store the settings and start the scan of your website.

3. Edit the result

If you checked the "Display edit screen after scan" checkbox, you'll see a page like this:

You can now adopt the settings to your needs. Press the "Create file" button to use this information for generation of the sitemap file.

4. Store sitemap

When you've pressed the button "Create file" in the result overview page the sitemap will be generated and written to the sitemap file specified at the settings page.

5. Inform Google

When the sitemap has been successfuly written to the filesystem you'll get the option to inform Google. Just press the "Submit to google" button.
Is this your first sitemap Google suggests to submit the sitemap within a Google Sitemaps account. You can get one at http://www.google.com/webmasters/sitemaps/. This is the only possibility to track the status of the Google sitemap at the moment - so please do so.
The message given by phpSitemapNG does only mean that Google got the url of the sitemap, not that it successfuly downloaded and computed the sitemap.

6. Watch your website within Google

That's it, you've successfuly created your Google sitemap.
So track the impact of Google Sitemaps you can query Google about the number of indexed pages: Type site:enarion.net (modify the website after site: to match your website). Then you'll see the number of indexed pages: Results 1-... of about x from ... Where x is the number of pages of your website that is integrated in the Google Search index at the moment. This number can differ depending on your location because of the not sychronized Google index.
Maybe you have some webpages in the result without description, only the url of the webpage. This means that Google got these urls (from the sitemap file) but does not have crawled, computed or added of this webpage to its index. It normally takes 1-5 days than there will be a description.

Next steps: Donate phpSitemapNG, give feedback

Father of ASP.Net2.0

2007-09-05T02:23:00.001+10:00

http://msdn2.microsoft.com/en-us/library/bb266332.aspx

Microsoft Architect Journal

Architecture Journal Profile: Scott Guthrie

Scott Guthrie is a general manager in Microsoft's Developer Division. He runs the development teams that build CLR (Common Language Runtime), ASP.NET, WPF (Windows Presentation Foundation), "WPF/E," Windows Forms, IIS (Internet Information Services) 7.0, Commerce Server, .NET Compact Framework, and the Visual Studio Web and Client Development Tools. As part of the new Architecture Journal Profile series, Ron Jacobs sat down with Scott to ask him about his career and thoughts regarding architecture. (Click here to go to Scott Guthrie's Career at Microsoft.)

RJ: Today, we're going to talk about you and your career for people who think, "This sounds like a cool job." What's your role now at Microsoft?

SG: I run our .NET developer platform group. This group includes the CLR (Common Language Runtime), the .NET Compact Framework, IIS (Internet Information Services), ASP.NET, Atlas, Commerce Server, Windows Presentation Foundation, Windows Forms, and our development tools for targeting Web applications in Visual Studio.

RJ: Wow, that's a lot of surface area!

SG: It's a lot of fun. It encompasses our core application models, the runtime, the tools, and all the engines they run on top of. It's a lot of cool stuff, and a lot of things to play with.

RJ: Most people will remember you from your association with ASP.NET. Let's go back to the early days here at Microsoft. How did you get started?

SG: I started with the IIS team back in '96-'97, working on our core Web server technologies, and was involved in shipping a version of IIS. After IIS 4 was released, we started looking at next-generation Web programming model pieces. At the time, we thought, "Maybe we're done. Is there anything left to do in terms of feature set?"

We started talking with a lot of customers and looked hard at the types of applications they were building. We very quickly learned that there was still a lot left to do. People were struggling with code/ content separation and how to write clean code. We used to joke that "write once, read never" code was being produced. From a tooling and runtime administration perspective, there were many challenges in making our existing infrastructure work really well. To help make this happen, we formed a small team to think about future architectures with IIS. This is the team that invented the HTTP.SYS kernel driver that we introduced with Windows Server 2003. With a colleague, I started looking at Web programming model pieces and wrote the initial prototype for what became ASP.NET.

RJ: It seems that you were thinking of taking this to the next level and taking advantage of something that was super secret at the time. I remember those days of .NET; you used to call it ASP+ back then.

SG: We originally called it XSP; and people would always ask what the X stood for. At the time it really didn't stand for anything. XML started with that; XSLT started with that. Everything cool seemed to start with an X, so that's what we originally named it. In the first six months, we didn't use .NET. The CLR didn't exist—it was just starting around the same time we were—so, we were doing most of our prototyping in C++, JavaScript, and ActiveScript script engines. We knew we wanted an object-oriented environment, and we really liked the characteristics a managed programming model provided in terms of garbage collection, nice encapsulation, and object-orientation techniques. We actually started writing production code in C++, though, because at the time we didn't really have a good runtime platform on which to build. We got about two weeks into it when we met up with the CLR team; at the time that team had no partners inside the company building on top of them. The only compiler they had was this thing called "simple managed C," which we affectionately called "smack." We ended up saying, "Maybe we should build on this." It was a huge risk, and at the time our team consisted of three or four people total. We were allowed to take a bet on it mainly because nobody really cared if we failed. Thankfully, we did and it paid off in a huge way. The rest is history, so to speak.

RJ: I remember those days. In the early days of the CLR, few people were willing to take that bet. Many teams said, "I don't think so," but you guys did, and it paid off in a wonderful way.

SG: Yeah, people were just terrified of the whole idea of garbage collection on the server, which we take for granted today. They said, "There is no way you can build an app with garbage collection running in the background. Your server will never scale." There were lots of doomsday scenarios. From a project perspective, one of the things we did paid off in a huge way. We said, "We're going to bet on managed code, and it won't be a wrapper around some native stuff. We're going to bake it deeply into the platform. We're going to write about 95 percent of our code in managed code itself."

The reason we did that was twofold. One was to take full advantage of the extensibility it provided and really bake object-oriented extensibility very deeply into the platform. And, second, we knew that customer applications would be managed code and that our percentage of code on a call stack would be relatively small compared to the customer's share. If even we didn't think we could write in managed code, we were kidding ourselves if we thought customer applications would sail. It was a great forcing function. From day one through creating more complicated samples, we were tuning the core CLR engine along the way, and that translated into a huge customer savings when we started getting more complicated customer applications on top. It was a good bet.

RJ: It's interesting that you look at this as a way to drive improvement down into the engine. You said, "Not only are we doing this, but we're making the engine better by doing so."

SG: I think that was a huge bet, but it was an approach that worked out well. The fact that we were a small team and starting with a new code base helped tremendously. If we had been a larger team or had an existing large legacy code base, it would have been more difficult, because COM interoperability didn't exist back then. But the fact that we were starting from scratch and able to start small really helped drive those core improvements deep into the engine. As we got bigger and our feature set flushed itself out, it just kept paying dividends.

RJ: I think it's cool that the people who were managing you let you make that call.

SG: It was definitely a gamble, but it was a calculated one. There was a huge upside if we could make it work, but the downside was that there were three or four of us, and we could always do something new the next year. Microsoft has often made these big bets, and usually they pay off in a big way. Occasionally, they don't—and they can fail spectacularly—but, as a company, we try to make sure that we bet big on a couple of key things.

RJ: Did you have to persuade anybody to let you take the risk, or was it easier than that?

SG: We certainly had to persuade a number of people along the way. One thing we did early in the project was get running code in prototypes that we could show people. Often when you're working on a project that's new or something that hasn't been done before, it's easy to put together a bunch of PowerPoint slides that sound good, but it's especially valuable to actually show code and walk people through code that's running. Not only does the prototype prove that it's real, but also you just learn a terrific amount by doing it.

One of the things I try to do with my team is to prototype early, build sample apps early, especially demo apps that we can walk the customer through and say, "Look, here's how you can build an app." We try to do that as early as possible to learn what works and what doesn't, so we can react accordingly. About a month and a half into the ASP project I wrote a prototype, and we were able to walk people through. Here was this component control-driven model—we didn't call them controls back then; they were declarative tags or components—and here was this event-driven way to program for the Web. We were able to build apps and discovered quickly that some of the things we had come up with were really impossible to code. At the same time, we learned that "it would be really cool to have this feature, or that feature," and we iterated along the way. That helped tremendously when we were trying to help people realize that we weren't complete lunatics. We were able to show code, and they were able to get it. It was still a gamble.

RJ: It almost sounds like the test-driven development mindset. Let's do short iterations; let's get to something that works. We'll eat our own dog food, and we'll write against our own APIs to understand what it feels like to use them.

SG: It's definitely the same type of principle. I differentiate between test-driven development as a methodology for how you can drive quality early and how you can provide a base that lets you refactor and adapt your code base without having to worry about regressions. We certainly follow that philosophy internally when we develop production code. I think there's also value in doing a prototype phase even before you get to production code. That's one of the successful things that we did with ASP.NET. We said that we're going to throw away every line of code we're going to write for the next couple of months. Let's all agree on that. We're not going to say, "Oh let's take this and adapt it; we can clean it up." No. We're going to throw it away. We're going to "deltree" this subdirectory at some point, and that way we can be more adventurous about trying new things. We don't have to worry about making sure that everything's robust because it's going to be in the final version.

We actually did that for a few months and said, "We're done, delete it; let's start over from scratch; now let's write the full production code and make sure we bake in quality at the time." I think a lot of teams could benefit from that. The hardest thing is making sure you delete the prototype code. Too often, projects develop with "Well, it's kind of close." It's very difficult to start with a prototype and make it robust. I'm a firm believer in starting with a prototype phase and then deleting it.

RJ: It demonstrates that we value the learning more than we value these files and these bits from the prototype phase.

SG: Every time you work on a project, if you rewrite anything, whether it's from scratch or not, the code gets better. Partly, it's because you understand the problems and pitfalls of the last approach and can reflect and improve on it. The challenge is that you can't easily do that time and time again. But when you're first starting out on a project or a brand-new area where it isn't clear how you get from Point A to the finished product, having a dedicated period where you prototype and try things out is super valuable.

RJ: Some people call that the "architectural spike." Here's a new area, and we're going to explore. Changing directions, though, what were you doing before you came to Microsoft?

SG: I actually joined Microsoft right out of college. I interned with Microsoft while I was in college. I was involved in a couple of startups in college and high school, did some development, and had some fun there, but I joined Microsoft straight out of college.

RJ: We've been talking to a lot of people who find architecture interesting. There seem to be very few people who are purely architects in that they just design stuff and never write code. Most people are a mix: They spend some time developing, some time architecting. What advice would you give to somebody who has been doing development but wants to do more architectural thinking?

SG: Writing code is valuable for an architect. Not necessarily production code you check in, but constantly trying out new technologies, new approaches, and feeling how the system works. I don't write a lot of production code these days, but I spend an hour or two every day writing code. It may be samples, prototypes, or some fun personal project—whatever it is, I'm trying things out, thinking of ways to structure things. Being hands-on is very valuable from a code architect's perspective.

The other thing I would recommend is taking a look at core systems theory and how to architect very robust systems. Consider some of the principles you want to think about and apply them as you're doing it. That doesn't mean thinking about what the lines of code look like, but thinking about simplicity, or robustness, or fault tolerance. Those types of things are core in successful systems; whether it's a client application, server application, or a game. An architect who thinks hard about those kinds of principles and can marry them with a good coding background can provide a tremendous amount of guidance to teams.

Those principles are not about playing with a wizard or checking out cool new stuff, but studying how the process-address space works in a Windows or Unix application. What is threading, and how do you deeply internalize what it looks like on a multiprocessor or multicore system? It's about absorbing that type of knowledge, thinking about its ramifications, and spending some focused time thinking hard about the trends, where the technology is going from a hardware and a software perspective, and considering how to adapt and take advantage of it. That's what I recommend doing.

RJ: At Microsoft we have developers, program managers, and architects. People are often curious about the role of the architect. What's your expectation for the role of the architect on the team?

SG: There are a couple of responsibilities that we hope or expect an architect to bring to a team. One is a very deep, solid background in architecture, development, and the software principles I was talking about. With that type of background, our hope is that a process of osmosis will take place—that some of it will rub off on other team members. Hallway conversations or informal office chats can provide a tremendous amount of leadership to a team, especially when you supervise junior and senior developers.

We look for an architect to pave the way regarding what the product should be doing from a technical perspective. Often architects do more advanced prototyping work and investigations of where we should take the product. We look to them to recommend where we should go, and from an implementation perspective, we ask them to look at both the next-generation product and the current product to identify areas we should clean up. For example, which areas should we factor slightly differently? What are some practices we can implement throughout the code base to improve it?

RJ: In addition to deep, solid, technical skills, what other attributes do you think contribute to a successful architect?

SG: The hardest thing, at least at Microsoft, is that very deep technical people who want to go up the architect track need to make sure that they can marry their technical skills to an ability to work both within and across teams in a company.

Some of those softer skills are harder to build, meaning that an architect needs to be hands-on, but to do so in a way that doesn't threaten developers or other teams. They should also avoid "I own this, you own that" conversations. Architects have to be able to work across teams very flexibly. They need to do so in a way that doesn't leave people feeling as if the architect is just diving into the most interesting problem for the moment and then flying off when things get hard. Other team members have to believe that the architect is committed to the team and is part of a long-term relationship that provides value on a problem. Those are the types of skills an architect needs to develop. The super-senior architects who have the biggest impact can marry deep, deep technical and design skills with people skills and collaborative abilities.

RJ: A lot of people tell me is that the rate of change is accelerating and new stuff is coming out all the time. You mentioned how important it is to stay up-to-date on these things, but there are only so many hours in the day. How do you stay up-to-date?

SG: It's hard, especially in the development space. When I think of the pace of innovation that's going on right now and the rate of information flow, I certainly can't remember a time when it was going this fast. I think back to a time, the Internet battles of the '90s, when Internet Explorer was competing with Netscape. At the time, it felt as if we were shipping constantly, and there was a lot going on.

From the development perspective, I think we're in a phase right now where the pace is even more accelerated than it was then. It is certainly very hard to stay up-to-date. You have to find time to do it. You have to spend focused time keeping an eye on what is happening. I think blogs are a great mechanism for doing that. I subscribe to Bloglines, which is a great free service. I probably subscribe to 300 or 400 blogs, and I try to spend 20 to 30 minutes a day in the morning and the evening reading through what everyone posts. It gives you a good sense of what the hot topics and the interesting ideas are.

Part of keeping up means spending an hour a day of focused time doing prototyping; trying things out, either with your own product or other technologies; getting a good grasp on what pieces are out there and how you can use them. The other important task, when you're looking at any new technology, API, methodology, or programming approach, is to look hard not just at the interesting thing itself, but also try to extrapolate its useful principles so you can apply them elsewhere. So, if it's a Java refactoring book, great. There are some specific Java refactorings there, but what are the broader refactoring concepts you can internalize and apply to VB or C#? If it's an AJAX JavaScript framework that's very good at doing one specific task, great. Now, step back and try to recognize which of its aspects could be applied on another JavaScript framework. An architect should be good at looking at something and extrapolating the interesting aspect in and of itself, as opposed to the individual element of the technology.

RJ: As you look back over your years here at MS, is there anything you regret?

SG: As you look back, there are things you would do differently. Sometimes, it might be a technical thing you've done, the way you've implemented a feature, and you think, "Everyone abuses that feature." Or they do things not quite the way we intended them to be done. Certainly, when we've built a development platform as broad as .NET, I could come up with a dozen or so things that in hindsight that I wish we had done slightly differently. There are also ways that you approach things, or ways that you work with different teams and think, "Gosh, I wish I'd handled that conversation slightly differently." So, there are definitely lots of individual examples I could come up with.

Overall, I'm happy about where .NET is, so we've been fairly successful with where we've taken it. But there are lots of things I wish we'd done slightly differently, such as, "Gosh, I wish we hadn't sealed that class," or, "Gosh, I wish we hadn't unsealed that class."

If there's one significant thing I wish we'd done differently, it would be that we'd spent more time early on thinking hard about the client installation process for building .NET client apps. I think the approach we took with a single redistributable that you download is not any worse than any other Windows redistributable, but I wish we'd taken the opportunity early on to get a less impactful installation and simplify client-app deployment. That is something we're spending a lot of time on right now, and it's going to get dramatically better in the future, but I wish we'd done that six years ago and spent more time thinking through some of those scenarios a bit earlier.

RJ: In your office you have all these speaker badges going way back, and you've had chances to go many places and meet a lot of people. What highlights have you had? Is there anybody in particular that sticks out in your mind?

SG: One of the things that's fun about working on a developer platform is just seeing the range and diversity of apps people have built on our stuff. Whether it's MySpace, which is the largest social-networking platform in the world—there are a billion-and-a-half page views a day using .NET—or the London Stock Exchange or National Health Service of the U.K., or a whole bunch of companies on Wall Street, Costco, Dell.com, or Match.com, there are tons of cool customer apps built on Microsoft technology. Many of these are on the Web; others use different technology. If you go to the Walt Disney World properties, the meters that run the "Fast Pass tickets" run on the compact framework and the CLR. If someone knocks on the door from the U.S. Census or the U.S. Postal Service, the device that person is holding also runs on the .NET Framework.

That, for me, is the highlight: seeing how .NET is being used all over the place. Sometimes in weird, whacky ways, sometimes for mission-critical apps, but each time in a unique way that, frankly, you might not have thought of. I think the hallmark of a good framework doesn't lie in the applications people build on it that you had expected them to build, but in the fact that customers and developers were able to take it far beyond what you had imagined. For me, that's the highlight of .NET.

Scott Guthrie's Career at Microsoft

Scott Guthrie joined Microsoft in 1997 and first worked on IIS4 and the Windows NT Option Pack. Shortly after its release, he designed and prototyped a new server programming model originally codenamed "XSP," and together with Mark Anders subsequently formed and staffed a new team in 1998 to build what would ultimately be called ASP.NET.

Scott became production unit manager (PUM) of the ASP.NET team in early 2002, and shipped ASP.NET V1.1 as part of Windows Server 2003. During this time he also led the incubation of the popular Web Matrix development tool, a free ASP.NET development tool that helped spark new thinking about tools for Web development, as well as a new approach for targeting programming hobbyists and enthusiasts. In late 2002 he also became PUM of the Web tool features within Visual Studio and was responsible for the development of the new Visual Web Developer standalone product that will ship as part of the Visual Studio 2005 family, as well as all Web development features in Visual Studio. Visual Web Developer and ASP.NET 2.0 entered their first widespread public beta in the summer of 2004 and will ship in the first half of 2007.

In late 2003, Scott's team merged with the IIS team, and he became PUM of a unified Web Platform and Tools team that combines the assets of IIS, ASP.NET, and Visual Studio. Concurrent with finishing up ASP.NET 2.0 and Visual Web Developer, the team is now actively developing the next major version of Microsoft's Web Application Server, which will ship as part of Longhorn.

Now a general manager in Microsoft's Developer Division, Scott runs the development teams that build CLR, ASP.NET, WPF, "WPF/E," Windows Forms, IIS 7.0, Commerce Server, .NET Compact Framework, and the Visual Studio Web and Client Development Tools.

Scott graduated with a degree in computer science from Duke University in 1997.

This article was published in the Architecture Journal, a print and online publication produced by Microsoft. For more articles from this publication, please visit the Architecture Journal website.

How web servers works

2007-08-20T05:21:00.001+10:00

http://computer.howstuffworks.com/web-server4.htm

How web servers works

Inside This Article

1. Introduction to How Web Servers Work

2. The Basic Process

3. Behind the Scenes

4. The Internet

5. Clients and Servers

6. IP Addresses

7. Domain Names

8. Name Servers

9. Ports

10. Protocols

11. Putting It All Together

12. Extras: Security

13. Extras: Dynamic Pages

14. Lots More Information

15. See all Internet articles

Introduction to How Web Servers Work

Have you ever wondered about the mechanisms that delivered this page to you? Chances are you are sitting at a computer right now, viewing this page in a browser. So, when you clicked on the link for this page, or typed in its URL ( uniform resource locator), what happened behind the scenes to bring this page onto your screen?

If you've ever been curious about the process, or have ever wanted to know some of the specific mechanisms that allow you to surf the Internet, then read on. In this article, you will learn how Web servers bring pages into your home, school or office. Let's get started!

The Basic Process

Let's say that you are sitting at your computer, surfing the Web, and you get a call from a friend who says, "I just read a great article! Type in this URL and check it out. It's at http://www.howstuffworks.com/web-server.htm." So you type that URL into your browser and press return. And magically, no matter where in the world that URL lives, the page pops up on your screen.

At the most basic level possible, the following diagram shows the steps that brought that page to your screen:

Your browser formed a connection to a Web server, requested a page and received it.

On the next page, we'll dig a bit deeper.

Behind the Scenes

If you want to get into a bit more detail on the process of getting a Web page onto your computer screen, here are the basic steps that occurred behind the scenes:

The browser broke the URL into three parts:
1. The protocol ("http")
2. The server name ("www.howstuffworks.com")
3. The file name ("web-server.htm")
The browser communicated with a name server to translate the server name "www.howstuffworks.com" into an IP Address , which it uses to connect to the server machine.
The browser then formed a connection to the server at that IP address on port 80. (We'll discuss ports later in this article.)
Following the HTTP protocol, the browser sent a GET request to the server, asking for the file "http://www.howstuffworks.com/web-server.htm." (Note that cookies may be sent from browser to server with the GET request -- see How Internet Cookies Work for details.)
The server then sent the HTML text for the Web page to the browser. (Cookies may also be sent from server to browser in the header for the page.)
The browser read the HTML tags and formatted the page onto your screen.

If you've never explored this process before, that's a lot of new vocabulary. To understand this whole process in detail, you need to learn about IP addresses, ports, protocols... The following sections will lead you through a complete explanation.

The Internet

So what is "the Internet"? The Internet is a gigantic collection of millions of computers, all linked together on a computer network. The network allows all of the computers to communicate with one another. A home computer may be linked to the Internet using a phone-line modem, DSL or cable modem that talks to an Internet service provider ( ISP). A computer in a business or university will usually have a network interface card (NIC) that directly connects it to a local area network (LAN ) inside the business. The business can then connect its LAN to an ISP using a high-speed phone line like a T1 line. A T1 line can handle approximately 1.5 million bits per second, while a normal phone line using a modem can typically handle 30,000 to 50,000 bits per second.

ISPs then connect to larger ISPs, and the largest ISPs maintain fiber-optic "backbones" for an entire nation or region. Backbones around the world are connected through fiber-optic lines, undersea cables or satellite links (see An Atlas of Cyberspaces for some interesting backbone maps). In this way, every computer on the Internet is connected to every other computer on the Internet.

Clients and Servers

In general, all of the machines on the Internet can be categorized as two types: servers and clients. Those machines that provide services (like Web servers or FTP servers) to other machines are servers. And the machines that are used to connect to those services are clients. When you connect to Yahoo! at www.yahoo.com to read a page, Yahoo! is providing a machine (probably a cluster of very large machines), for use on the Internet, to service your request. Yahoo! is providing a server. Your machine, on the other hand, is probably providing no services to anyone else on the Internet. Therefore, it is a user machine, also known as a client. It is possible and common for a machine to be both a server and a client, but for our purposes here you can think of most machines as one or the other.

A server machine may provide one or more services on the Internet. For example, a server machine might have software running on it that allows it to act as a Web server, an e-mail server and an FTP server. Clients that come to a server machine do so with a specific intent, so clients direct their requests to a specific software server running on the overall server machine. For example, if you are running a Web browser on your machine, it will most likely want to talk to the Web server on the server machine. Your Telnet application will want to talk to the Telnet server, your e-mail application will talk to the e-mail server, and so on...

IP Addresses

To keep all of these machines straight, each machine on the Internet is assigned a unique address called an IP address. IP stands for Internet protocol, and these addresses are 32-bit numbers, normally expressed as four "octets" in a "dotted decimal number." A typical IP address looks like this:

          216.27.61.137

The four numbers in an IP address are called octets because they can have values between 0 and 255, which is 2⁸ possibilities per octet.

Every machine on the Internet has a unique IP address. A server has a static IP address that does not change very often. A home machine that is dialing up through a modem often has an IP address that is assigned by the ISP when the machine dials in. That IP address is unique for that session -- it may be different the next time the machine dials in. This way, an ISP only needs one IP address for each modem it supports, rather than for each customer.

If you are working on a Windows machine, you can view a lot of the Internet information for your machine, including your current IP address and hostname, with the command WINIPCFG.EXE (IPCONFIG.EXE for Windows 2000/XP). On a UNIX machine, type nslookup at the command prompt, along with a machine name, like www.howstuffworks.com -- e.g. "nslookup www.howstuffworks.com " -- to display the IP address of the machine, and you can use the command hostname to learn the name of your machine. (For more information on IP addresses, see IANA.)

As far as the Internet's machines are concerned, an IP address is all you need to talk to a server. For example, in your browser, you can type the URL http://209.116.69.66 and arrive at the machine that contains the Web server for HowStuffWorks. On some servers, the IP address alone is not sufficient, but on most large servers it is -- keep reading for details.

Domain Names

Because most people have trouble remembering the strings of numbers that make up IP addresses, and because IP addresses sometimes need to change, all servers on the Internet also have human-readable names, called domain names. For example, www.howstuffworks.com is a permanent, human-readable name. It is easier for most of us to remember www.howstuffworks.com than it is to remember 209.116.69.66.

The name www.howstuffworks.com actually has three parts:

The host name ("www")
The domain name ("howstuffworks")
The top-level domain name ("com")

Domain names within the ".com" domain are managed by the registrar called VeriSign. VeriSign also manages ".net" domain names. Other registrars (like RegistryPro, NeuLevel and Public Interest Registry) manage the other domains (like .pro, .biz and .org). VeriSign creates the top-level domain names and guarantees that all names within a top-level domain are unique. VeriSign also maintains contact information for each site and runs the "whois" database. The host name is created by the company hosting the domain. "www" is a very common host name, but many places now either omit it or replace it with a different host name that indicates a specific area of the site. For example, in encarta.msn.com, the domain name for Microsoft's Encarta encyclopedia, "encarta" is designated as the host name instead of "www."

Name Servers

The whois CommandOn a UNIX machine, you can use the whois command to look up information about a domain name. You can do the same thing using the whois form at VeriSign. If you type in a domain name, like "howstuffworks.com," it will return to you the registration information for that domain, including its IP address.

A set of servers called domain name servers (DNS) maps the human-readable names to the IP addresses. These servers are simple databases that map names to IP addresses, and they are distributed all over the Internet. Most individual companies, ISPs and universities maintain small name servers to map host names to IP addresses. There are also central name servers that use data supplied by VeriSign to map domain names to IP addresses.

If you type the URL "http://www.howstuffworks.com/web-server.htm" into your browser, your browser extracts the name " www.howstuffworks.com," passes it to a domain name server, and the domain name server returns the correct IP address for www.howstuffworks.com. A number of name servers may be involved to get the right IP address. For example, in the case of www.howstuffworks.com, the name server for the "com" top-level domain will know the IP address for the name server that knows host names, and a separate query to that name server, operated by the HowStuffWorks ISP, may deliver the actual IP address for the HowStuffWorks server machine.

On a UNIX machine, you can access the same service using the nslookup command. Simply type a name like "www.howstuffworks.com" into the command line, and the command will query the name servers and deliver the corresponding IP address to you.

So here it is: The Internet is made up of millions of machines, each with a unique IP address. Many of these machines are server machines, meaning that they provide services to other machines on the Internet. You have heard of many of these servers: e-mail servers, Web servers, FTP servers, Gopher servers and Telnet servers, to name a few. All of these are provided by server machines.

Ports

Any server machine makes its services available to the Internet using numbered ports, one for each service that is available on the server. For example, if a server machine is running a Web server and an FTP server, the Web server would typically be available on port 80, and the FTP server would be available on port 21. Clients connect to a service at a specific IP address and on a specific port.

Each of the most well-known services is available at a well-known port number. Here are some common port numbers:

echo 7
daytime 13
qotd 17 (Quote of the Day)
ftp 21
telnet 23
smtp 25 (Simple Mail Transfer, meaning e-mail)
time 37
nameserver 53
nicname 43 (Who Is)
gopher 70
finger 79
WWW 80

If the server machine accepts connections on a port from the outside world, and if a firewall is not protecting the port, you can connect to the port from anywhere on the Internet and use the service. Note that there is nothing that forces, for example, a Web server to be on port 80. If you were to set up your own machine and load Web server software on it, you could put the Web server on port 918, or any other unused port, if you wanted to. Then, if your machine were known as xxx.yyy.com, someone on the Internet could connect to your server with the URL http://xxx.yyy.com:918. The ":918" explicitly specifies the port number, and would have to be included for someone to reach your server. When no port is specified, the browser simply assumes that the server is using the well-known port 80.

Protocols

Once a client has connected to a service on a particular port, it accesses the service using a specific protocol. The protocol is the pre-defined way that someone who wants to use a service talks with that service. The "someone" could be a person, but more often it is a computer program like a Web browser. Protocols are often text, and simply describe how the client and server will have their conversation.

Perhaps the simplest protocol is the daytime protocol. If you connect to port 13 on a machine that supports a daytime server, the server will send you its impression of the current date and time and then close the connection. The protocol is, "If you connect to me, I will send you the date and time and then disconnect." Most UNIX machines support this server. If you would like to try it out, you can connect to one with the Telnet application. In UNIX, the session would look like this:

%telnet web67.ntx.net 13 Trying 216.27.61.137... Connected to web67.ntx.net. Escape character is '^]'. Sun Oct 25 08:34:06 1998 Connection closed by foreign host.

On a Windows machine, you can access this server by typing "telnet web67.ntx.net 13" at the MSDOS prompt.

In this example, web67.ntx.net is the server's UNIX machine, and 13 is the port number for the daytime service. The Telnet application connects to port 13 (telnet naturally connects to port 23, but you can direct it to connect to any port), then the server sends the date and time and disconnects. Most versions of Telnet allow you to specify a port number, so you can try this using whatever version of Telnet you have available on your machine.

Most protocols are more involved than daytime and are specified in Request for Comment (RFC) documents that are publicly available (see http://sunsite.auc.dk/RFC/ for a nice archive of all RFCs). Every Web server on the Internet conforms to the HTTP protocol, summarized nicely in The Original HTTP as defined in 1991 . The most basic form of the protocol understood by an HTTP server involves just one command: GET. If you connect to a server that understands the HTTP protocol and tell it to "GET filename," the server will respond by sending you the contents of the named file and then disconnecting. Here's a typical session:

%telnet www.howstuffworks.com 80 Trying 216.27.61.137... Connected to howstuffworks.com. Escape character is '^]'. GET http://www.howstuffworks.com/ <html> <head> <title>Welcome to How Stuff Works</title>   ... </body> </html> Connection closed by foreign host.

In the original HTTP protocol, all you would have sent was the actual filename, such as "/" or "/web-server.htm." The protocol was later modified to handle the sending of the complete URL. This has allowed companies that host virtual domains, where many domains live on a single machine, to use one IP address for all of the domains they host. It turns out that hundreds of domains are hosted on 209.116.69.66 -- the HowStuffWorks IP address.

Putting It All Together

Now you know a tremendous amount about the Internet. You know that when you type a URL into a browser, the following steps occur:

The browser breaks the URL into three parts:
1. The protocol ("http")
2. The server name ("www.howstuffworks.com")
3. The file name ("web-server.htm")
The browser communicates with a name server to translate the server name, "www.howstuffworks.com," into an IP address, which it uses to connect to that server machine.
The browser then forms a connection to the Web server at that IP address on port 80.
Following the HTTP protocol, the browser sends a GET request to the server, asking for the file "http://www.howstuffworks.com/web-server.htm." (Note that cookies may be sent from browser to server with the GET request -- see How Internet Cookies Work for details.)
The server sends the HTML text for the Web page to the browser. (Cookies may also be sent from server to browser in the header for the page.)
The browser reads the HTML tags and formats the page onto your screen.

Extras: Security

You can see from this description that a Web server can be a pretty simple piece of software. It takes the file name sent in with the GET command, retrieves that file and sends it down the wire to the browser. Even if you take into account all of the code to handle the ports and port connections, you could easily create a C program that implements a simple Web server in less than 500 lines of code. Obviously, a full-blown enterprise-level Web server is more involved, but the basics are very simple.

Most servers add some level of security to the serving process. For example, if you have ever gone to a Web page and had the browser pop up a dialog box asking for your name and password, you have encountered a password-protected page. The server lets the owner of the page maintain a list of names and passwords for those people who are allowed to access the page; the server lets only those people who know the proper password see the page. More advanced servers add further security to allow an encrypted connection between server and browser, so that sensitive information like credit card numbers can be sent on the Internet.

That's really all there is to a Web server that delivers standard, static pages. Static pages are those that do not change unless the creator edits the page.

Extras: Dynamic Pages

But what about the Web pages that are dynamic? For example:

Any guest book allows you to enter a message in an HTML form, and the next time the guest book is viewed, the page will contain the new entry.
The whois form at Network Solutions allows you to enter a domain name on a form, and the page returned is different depending on the domain name entered.
Any search engine lets you enter keywords on an HTML form, and then it dynamically creates a page based on the keywords you enter.

In all of these cases, the Web server is not simply "looking up a file." It is actually processing information and generating a page based on the specifics of the query. In almost all cases, the Web server is using something called CGI scripts to accomplish this feat. CGI scripts are a topic unto themselves, and are described in the HowStuffWorks article How CGI Scripting Work.

For more information on Web servers and related topics, check out the links on the next page.

Lots More Information

Cannot Access shared resources on a LAN computer

2007-08-16T22:52:00.001+10:00

http://www.softwaretipsandtricks.com/forum/windows-xp/17296-cannot-access-shared-resources-computer.html

Two computers A and B are on a network having Windows XP. From Computer A, I can see the shared resources in Computer B. But I cannot see the shared resources of Computer A from Computer B. I can ping Computer B from Computer A and also the same form Computer A to Computer B. So the network seems to work fine. What could be the problem. Can any one help me?

Regards,
Satish

If you have win xp home edition, this is the only way to get over the problem as the local settings & sedurity policy are not available in Administration Tools.
As far as I know, user rights policies applies to WinXP Home as well, you just don't have a builtin GUI tool to see/change them.

You should be able to set/remove those privileges with the Windows 2003 resource kit command line tool ntrights.exe.

Ntrights.exe is in the free Win2k3 resource kit:

Windows Server 2003 Resource Kit Tools
http://go.microsoft.com/fwlink/?LinkId=4544
or
http://www.microsoft.com/downloads/d...displaylang=en
The kit will install on WinXP or later.

After installation, click on: Start, All Programs, Windows Resource Kit Tools, Command Shell

Then enter the following commands. (Attention: they are case sensitive.)

net user guest /active:yes
ntrights +r SeNetworkLogonRight -u Guest
ntrights -r SeDenyNetworkLogonRight -u Guest

The first command enables network access for Guest, the two subsequent ones change two different policies to allow network access for Guest.

This has been confirmed to work by several users.

Technology

2007-08-15T21:13:00.001+10:00

php
javascript
Vbscript
Mysql
Apache
xml
Ajax

Google Webmaster | sitemap-generator

2007-08-12T00:14:00.001+10:00

https://www.google.com/webmasters/tools/docs/en/sitemap-generator.html

Webmaster Tools

About Webmaster Tools

Using the Sitemap Protocol

Using the Sitemap Generator

Google Webmaster Central

Contents

Before you begin
Downloading the Sitemap Generator program files
Creating a configuration file
Uploading the files to your web server
Running the Sitemap Generator script
Submitting your Sitemap to Google
Troubleshooting

Before you begin

The Google Sitemap Generator is a Python script that creates a Sitemap for your site using the Sitemap Protocol. This script can create Sitemaps from URL lists, web server directories, or from access logs. In order to use this script:

You must be able to connect to and run scripts on your web server.
Your web server must have Python 2.2 or later installed.
You must know the command that launches Python. (Generally, this is python, but may vary by installation. For instance, if the web server has two versions of Python installed, the earlier version may be invoked by the command python and the later version may be invoked by the command python2.)
You must know the directory path to your site. If your web server hosts one site, this may be a path such as var/www/html. If you have a virtual server that hosts multiple sites, this may be a path such as home/virtual/site1/fst/var/www/html.
You must be able to upload files to your web server (for instance, using FTP).
If you will be generating a list of URLs based on access logs, you must know the encoding used for those logs and the complete path to them.

If you aren't sure about any of this, you can check with your web hosting company.

Now you're ready to get started. Here's an overview of what you'll need to do.

Download the Sitemap Generator program files. Extract the files to a local directory.
Create a configuration file for your site using the provided example_config.xml file as a template. Modify this file as needed for your site and save it.
Upload the necessary files to your web server.
Run sitemap_gen.py.
Add the generated Sitemap to your Google webmaster tools account.
Set up a recurring script. (optional)

If you are unable to use the Sitemap Generator, you can add a Sitemap to your Google webmaster tools account in another format, such as a simple text file.You can also find links to third-party programs that support Google Sitemaps here.

For News Sitemaps: The Sitemap Generator is not recommended for use in creating Google News Sitemaps at this time, due to the special requirements of News Sitemaps. News Sitemaps are intended to be dynamic lists of only the most recently published news articles (rather than the entire website), and they are updated frequently.

1. Downloading the Sitemap Generator program files

The Sitemap Generator files are available in ZIP and GZ archive formats from the following location:

http://sourceforge.net/project/showfiles.php?group_id=137793&package_id=153422

Once you download the archive, extract it into a local directory. Locate the following files:

README —contains the latest information about this tool
sitemap_gen.py —the python script that generates your Sitemap
example_config.xml —the template configuration file you'll use to specify the configuration for your site
example_urllist.txt —the template URL list you can use if you wish to create a Sitemap based on a set of URLs that you specify

2a. Creating a configuration file

This section provides step-by-step instructions for creating a configuration file. It also provides a complete reference of the options available. If you are creating Mobile Sitemaps, see the additional mobile guidelines.

In order to create a configuration file for your site, you must have the following information:

The base URL for your site (such as http://www.example.com/). Only URLs that begin with this base URL can be included in the Sitemap. Ensure that you include the protocol (such as http://). For instance, http://www.google.com is a valid base url, but www.google.com is not.
The web server path to the location where you want to store the Sitemap. Generally, this is the path to the base URL as the Sitemap cannot contain URLs that are in a higher-level directory from the location of the Sitemap. When you run the Google Sitemap Generator, it creates the Sitemap and places it in the location you specify.
The methods you want the Sitemap Generator to use to create your Sitemap. You can use any combination of methods. The following methods are available:

URL —list individual URLs in this section of the configuration file, along with information about each URL. You would generally use this method in conjunction with another method to manually include additional URLs that other methods wouldn't pick up.
URL list —point the configuration file to a text file that contains a list of URLs. You might want to use this method if this text file already exists or if you use a script to generate a list of URLs.
Directory paths —specify the directory paths for your site and corresponding URLs to those paths. The Sitemap Generator will create a list of URLs based on the contents of those directories. You might want to use this method if your site consists of static HTML files.
Access logs —point to the path to your log files. The Sitemap Generator will create a list of URLs based on the URLs included in the logs. You might want to use this method if your site consists of dynamic pages.
Sitemap —point to existing Sitemaps that you have created with the Sitemap Generator. The Sitemap Generator will create a single Sitemap that includes the URLs contained in each Sitemap. You could use this method if you have already created several smaller Sitemaps that you want to combine into one larger Sitemap.

Create the configuration file as follows:

Open the example_config.xml file in a text editor. Save it as a new file (such as config.xml or mysite_config.xml).

Locate the site definition section:

<site  base_url="http://www.example.com/"  store_into="/var/www/docroot/sitemap.xml.gz" verbose="1">

Change the base_url value to the URL for your site.

Change the store_into value to the path on your web server where you want to store the Sitemap and the filename you want to use for the Sitemap. Generally, this is the path to the base URL since Google can only accept URLs that are at the same level as or subdirectories of the directory that holds the Sitemap. You can specify a relative path from the directory where you upload the script or a complete path from the root of your web server. If you upload the script to your base URL directory, you can simply specify the filename.

Locate the generation method sections that begin with ** MODIFY or DELETE **. Each of these sections corresponds to a method for generating a Sitemap.

Delete the sections for the methods you aren't going to use.

Follow the instructions below for the methods you are going to use.

URL

Locate the following section:

<!-- ** MODIFY or DELETE **  "url" nodes specify individual URLs to include in the map. <br>  Required attributes:  href - the URL  Optional attributes:  lastmod - timestamp of last modification (ISO8601 format)  changefreq - how often content at this URL is usually updated priority - value 0.0 to 1.0 of relative importance in your site  -->   <url href="http://www.example.com/stats?q=name" />  <url  href="http://www.example.com/stats?q=age"  lastmod="2004-11-14T01:00:00-07:00"  changefreq="yearly"  priority="0.3" />

This section gives two examples: the first includes only the required attribute and the second includes the required attribute as well as the optional attributes.

Use this format for each of the URLs you want to include. The changefreq attribute gives Google a general idea of how often the URL is updated. This helps Google know how often to visit the page for new content. The priority attribute gives Google information about the relative importance of this page compared to the other pages of your site. This attribute has no effect on how Google compares your page to pages on other sites, it just helps Google know which pages of your site that you think are most important.

URL list

Locate the following section:

<!-- ** MODIFY or DELETE ** "urllist" nodes name text files with lists of URLs.  An example file "example_urllist.txt" is provided.   Required attributes:  path - path to the file   Optional attributes:  encoding - encoding of the file if not US-ASCII  -->  <urllist path="example_urllist.txt" encoding="UTF-8" />

Use this format to point to the path and name of the text file that contains your list of URLs. You can use the provided example_urllist.txt file as a template for that text file. You can specify either a relative or complete path to your web server. For instance, if the Sitemap Generator and urlist.txt file are located in the same directory, you can simply specify the filename of the .txt file, If you create a text file with an encoding other than UTF-8, you can use the encoding attribute to indicate this encoding. If you have multiple .txt files, you can use wildcards. For instance:

<urllist path="example_urllist*.txt" encoding="UTF-8" />

For each URL you include in the text file, you can specify the last modification date, change frequency, and priority. See the URLlist text file reference section for complete information about the structure of this file.

Directory paths

Locate the following section:

<!-- ** MODIFY or DELETE **  "directory" nodes tell the script to walk the file system and  include all files and directories in the Sitemap.  Required attributes: path - path to begin walking from  url - URL equivalent of that path   Optional attributes: default_file - name of the index or default file for directory URLs  -->   <directory  path="/var/www/icons"    url="http://www.example.com/images/" />
  <directory
     path="/var/www/docroot"
     url=" http://www.example.com/"
    default_file="index.html"
  />

This section gives two examples. If all of your pages are contained in subdirectories of one path, then you only need to include one entry. However, if you have multiple paths to pages on your site, include an entry for each.

Remember that each URL must begin with the base URL you specified in step 3. For instance, the examples given in the example_config.xml file both have URLs that begin with http://www.example.com/. Therefore, both URLs are valid.

Replace the example entries with entries for your site. Many sites will only have one entry that points to the base URL. Ensure that path value is the complete path to the directory on your web server. Ensure that the url value is the complete URL, including the protocol (such as http) and a trailing slash, if required.

You can use the default_file parameter to specify the filename that your server uses as the default page for a directory. In the above example, /var/www/docroot resolves to http://www.example.com/index.html. You are not required to specify this. However, if you do, the Sitemap Generator will include the page that maps to each subdirectory only once (rather than list both the directory URL and filename URL) and will use the last modified date of the file (rather than the directory) to extract the lastmod attribute for that page.

Access logs

Locate the following section:

<!-- ** MODIFY or DELETE ** "accesslog" nodes tell the script to scan webserver log files to extract URLs on your site.  Both Common Logfile Format (Apache's default  logfile) and Extended Logfile Format (IIS's default logfile) can be read. 				 Required attributes:  path - path to the file Optional attributes:  encoding - encoding of the file if not US-ASCII   --> <accesslog path="/etc/httpd/logs/access.log" encoding="UTF-8" /> <accesslog path="/etc/httpd/logs/access.log.0" encoding="UTF-8" /> <accesslog path="/etc/httpd/logs/access.log.1.gz" encoding="UTF-8" />

This section gives three examples. You should replace these entries and include an entry for each log file. Ensure that the path value is the complete path and filename on your web server. If the log files are not encoded as US-ASCII or UTF-8, then use the optional encoding attribute to specify the encoding. Rather than list each log file, you can use wildcards. For instance, in the above example, you could include the following entry that would include all three log files:

<accesslog path="/etc/httpd/logs/access.log*" encoding="UTF-8" />

The Sitemap Generator assigns priority to URLs it finds in the logs based on how often each URL is accessed. For instance, a URL that has been accessed 100 times will be given a higher priority than a URL that has been accessed twice. The actual priority assignment is relative and depends on each URL as compared to other URLs in the site.

sitemap

Locate the following section:

 <!-- ** MODIFY or DELETE **
     "sitemap" nodes tell the script to scan other Sitemap files.  This can     be useful to aggregate the results of multiple runs of this script into a single Sitemap. 				  Required attributes:   path - path to the file   --> <sitemap path="/var/www/docroot/subpath/sitemap.xml" />

This section gives one example. You should replace this entry and include an entry for each Sitemap you want to include. Ensure that the path value is the complete path and filename on your web server. You can list gzipped Sitemaps as well, as long as they have a .gz extension. Rather than list each Sitemap, you can use wildcards. For instance, the following entry would include any Sitemaps that begin with the word "sitemap" and have an .xml extension:

<sitemap path="/var/www/docroot/subpath/sitemap*.xml" />

The Sitemap Generator extracts all URLs and the optional data listed for each URL for every Sitemap you list and creates one Sitemap with this information. At this time, we can't guarantee that this method will work Sitemaps created with tools other than the Sitemap Generator.

Locate the filter definition section:

<!-- ********************************************************          FILTERS 				 Filters specify wild-card patterns that the script compares against all URLs it finds. Filters can be used to exclude certain URLs from your Sitemap, for instance if you have hidden content that you hope the search engines don't find.  Filters can be either type="wildcard", which means standard path wildcards (* and ?) are used to compare against URLs,  or type="regexp", which means regular expressions are used to compare.  Filters are applied in the order specified in this file. An action="drop" filter causes exclusion of matching URLs. An action="pass" filter causes inclusion of matching URLs, shortcutting any other later filters that might also match. If no filter at all matches a URL, the URL will be included. Together you can build up fairly complex rules.  The default action is "drop". The default type is "wildcard".  You can MODIFY or DELETE these entries as appropriate for your site. However, unlike above, the example entries in this section are not contrived and may be useful to you as they are. ********************************************************* -->  <!-- Exclude URLs that end with a '~' (IE: emacs backup files) --> <filter action="drop" type="wildcard" pattern="*~" />  <!-- Exclude URLs within UNIX-style hidden files or directories --> <filter action="drop" type="regexp" pattern="/\.[^/]*" />

You can use filtering to exclude specific URLs from the generated Sitemap. You might want to do this to create a cleaner list, to reduce redundant listings, or to keep certain URLs from being indexed. Note that if you use a robots.txt file to keep URLs from being indexed, then even if the URLs are included in your Sitemap, Google will not search or index them.

You can use any or all of the filtering methods. You can delete the entries you don't need and can create additional entries, if desired. Below are sample usages.

<filter action="drop" type="wildcard" pattern="*.jpg" />

This filter excludes URLs that end in .jpg. You might want to include a similar filter if all of your site's images are embedded within HTML pages and should not be accessed as standalone URLs.

<filter action="pass" type="wildcard" pattern="*.htm*" /> <filter action="drop" type="wildcard" pattern="*" />

This filter includes all .htm* files but excludes everything else.

Once you have made all the changes for your site, save the file.

Config File Syntax Reference

A complete explanation of the config file syntax is below. Each tag begins with a code sample, followed by a description of the attributes.

site
Required tag at the beginning of each config file.

<site base_url="http://www.example.com/" store_into="/var/www/html/sitemap.xml.gz" verbose="1" supress_search_engine_notify="1" default_encoding="UTF-8">

base_url	required	The HTTP path of the base of your website - only URLs that begin with this base can be included in the Sitemap
store_into	required	The web server path to the desired output file. The script will create this file - there's no need to create the file before running the script.
verbose	optional	Enter a number from 0-3, with higher numbers corresponding to increased debug information
suppress_search_engine_notify	optional	Disable search engine notification by entering "1" for testing purposes
default_encoding	optional	Specify a character encoding to be applied to file system paths and URLs

url
Optional tag that you can use to list each URL in your site.

<url href="http://www.example.com/stats?q=age"  lastmod="2004-11-14T01:00:00-07:00"  changefreq="yearly"  priority="0.3" />

href	required	The HTTP path of the base of your website - only URLs that begin with this base can be included in the Sitemap
lastmod	optional	The time the URL was last modified in W3C Datetime format (YYYY-MM-DDThh:mm:ss+00:00). You may omit the time portion. Examples: "2005-02-21T18:00:15+00:00" "2005-02-21"
changefreq	optional	The frequency with which the URL is likely to change. This is considered a hint and not a command. The value must be one of "always", "hourly", "daily", "weekly", "monthly", "yearly", or "never".
priority	optional	The priority of this page relative to other pages on the same site. The value is a number between 0.0 and 1.0, where 0.0 is the lowest priority and 1.0 is the highest priority. The priority can affect the order that search engines select URLs to explore on your site. Since the priority is relative, it is only used to select between URLs within your own site; the priority of your pages will not be compared to the priority of pages on other sites.

urllist
Optional tag that you can use to point to a text file that contains a list of the URLs in your site.

<urllist path="/var/www/html/urllist.txt" encoding="UTF-8" />

path	required	The path and filename of the .txt file. You can specify either a relative or complete path.
encoding	optional	The encoding of the file, if not UTF-8.

The urllist.txt file is a simple text file containing a list of URLs to map. You can also include optional attributes for each URL. Attributes are entered on the same line as the URL and are separated by a single space. For example:

http://www.example.com/abc/something http://www.example.com/abc/xyy.pdf lastmod=2001-12-31T14:05:06+00:00 http://www.example.com/abc/def?x=12&y=23 changefreq=weekly priority=0.3

lastmod	optional	The time the URL was last modified in W3C Datetime format (YYYY-MM-DDThh:mm:ss+00:00). You may omit the time portion. Examples: "2005-02-21T18:00:15+00:00" "2005-02-21"
changefreq	optional	The frequency with which the URL is likely to change. This is considered a hint and not a command. The value must be one of "always", "hourly", "daily", "weekly", "monthly", "yearly", or "never".
priority	optional	The priority of this page relative to other pages on the same site. The value is a number between 0.0 and 1.0, where 0.0 is the lowest priority and 1.0 is the highest priority. The priority can affect the order that search engines select URLs to explore on your site. Since the priority is relative, it is only used to select between URLs within your own site; the priority of your pages will not be compared to the priority of pages on other sites.

directory
Optional tag that you can use to specify directories in your site so the Sitemap Generator can create a list of URLs from the files found in those directories.

-->   <directory  path="/var/www/icons"    url="http://www.example.com/images/" />
  <directory
     path="/var/www/docroot"
     url=" http://www.example.com/"
    default_file="index.html"
  />

path	required	States the initial path. Sitemap Generator will traverse this directory and all subdirectories.
url	required	Specifies the URL equivalent of the path value.
default_file	optional	Specifies the default file for a directory on the server.

accesslog
Optional tag that you can use to specify the path and filename of IIS and Apache-style access logs so the Sitemap Generator can automatically pick up URLs from them.

 <accesslog path="/etc/httpd/logs/access-0.log" encoding="UTF-8"/>

path	required	States the path to the file.
encoding	optional	Specifies encoding of the file, if not UTF-8.

sitemap
Optional tag that you can use to specify the path and filename of existing Sitemaps that you have created with the Sitemap Generator. The Sitemap Generator will create a single Sitemap that includes the URLs contained in each Sitemap.

<sitemap path="/var/www/docroot/subpath/sitemap.xml" />

path

required

States the path to the Sitemap file.

filter
Optional tag that you can use to build rules that include or exclude specific files. Filters are obeyed in the order in which they appear in the config.xml file. However, intermixing filter entries and input entries (url, urllist, directory, or accesslog) has no additional effect - every URL the Sitemap Generator adds to the Sitemap is first compared against every filter. If no filter matches a URL, the default is to include the URL in the Sitemap.

<filter action="drop" type="wildcard" pattern="*/internal/*" />

action

optional

The action the filter should take. Valid values are:

drop - excludes matching URLs. This is the default action, so if no action is specified, the generator assumes "drop".
pass - includes matching URLs.

type

optional

The type of filtering. Valid values are:

wildcard - standard path wildcards (? and *) are used to compare against URLs. This is the default type, so if no type is specified, the generator assumes "wildcard".
regexp - regular expressions are used.

pattern

required

Specifies the pattern to match against.

Encodings

Files referenced by your configuration file, either URL lists or web server logs, can use encodings other than the default UTF-8. You can specify alternate encodings in config.xml to affect how the Sitemap Generator reads your files. Some common encodings are:

encoding="utf-8" is the assumed default
encoding="ascii" is a subset of UTF-8 so you don't have to specify it
encoding="iso-8859-1" is common for many west European languages

2b. Additional information for creating a mobile configuration file

You create a configuration file for a Mobile Sitemap in the same way as for a non-mobile Sitemap. However, you must create a separate config file for each markup language and run the Sitemap Generator with each config file separately so that you create a separate Sitemap for each.

Each config file must:

Specify a different filename for the store_into value.
Use filters to specify the URLs to exclude and include for the markup language. Remember that each Sitemap should include URLs for only one markup language. This means that the same URL may be included in multiple Sitemaps, if those URLs serve multiple markup languages.

Examples of filtering

Below are some examples of how you can use extension-based filters to generate Mobile Sitemaps for different markup languages. The specific filtering you use should be based on the types of markup languages used in your site, and how you specify each type. If you have implemented the details of your site differently (for instance, you may organize URLs with different markup languages in separate folders), you should filter based on the specifics of your site implementation. Remember that filters are applied in the order you list them in the config file. So, the first filter you should list is a "pass" action that specifies the URLs you want to include in the Sitemap.

To create a Sitemap for WML (WAP 1.2) content:

<filter action="pass" type="wildcard" pattern="*.wml" /> <filter action="drop" type="wildcard" pattern="*.*" />

To create a Sitemap for XHTML mobile profile (WAP 2.0) content:

<filter action="pass" type="wildcard" pattern="*.xhtml" /> <filter action="drop" type="wildcard" pattern="*.*" />

3. Uploading the files to your web server

You should upload the following files to your web server in a location you can access from a command line:

config.xml —this is the configuration file you just created using example_config.xml.
sitemap_gen.py —this is the Python script that generates your Sitemap.
urllist.txt —this file is optional; you only need to include it if you used the text file method of generating a Sitemap.

The method you use to upload these files depends on your environment. Common methods include FTP and SCP. For more information, contact your web host.

4. Running the Sitemap Generator script (sitemap_gen.py)

In order to run the Sitemap Generator, you'll need to connect to your web server. The method you use to connect depends on your environment. For instance, you can generally access a UNIX-based server using SSH. For more information on connecting to your web server and running scripts, talk to your web host.

Once you have copied the files to your web server, you'll need to run the Sitemap Generator script. Connect to your web server and run the following command (replace <path/config.xml> with the path to and filename of your configuration file; if you have uploaded this file to the same location as the Python script, you can exclude the path):

python sitemap_gen.py --config=<path/config.xml>

For instance, a UNIX-based command line might look similar to this:

A MS-DOS-based command shell might look similar to this:

Tip: If you're testing your configuration and are not ready to submit your Sitemap, the following syntax will prevent Sitemap Generator from contacting Google:


	$ python sitemap_gen.py --config= config.xml --testing

You'll see the status of your request in the command prompt:

	 	Reading configuration file: /path/config.xml 	Opened URLLIST "/path/urllist.txt" 	Walking DIRECTORY "/var/www/html/dir" 	Walking DIRECTORY "/var/www/html/dir2" 	Opened ACCESSLOG "/etc/httpd/logs/access-0.log" 	Sorting and normalizing collected URLs. 	Writing Sitemap file "/path/sitemap.xml.gz" with 1092 URLs 	Notifying search engines. 	Notifying www.google.com 	Count of file extensions on URLs: 		208  .html 		574  .jpg 		... 		Number of errors: 0 		Number of warnings: 0

If you don't see very much output like this, remember that the verbose setting in your configuration file affects how much information is printed on the screen. This example is representative of setting verbose to "1".

Any errors in the file will also be returned. For instance, if you leave the url= attribute off a directory entry, the script will output the following:

	 	[ERROR] Directory entries must have both "path" and "url" attributes 	Number of errors: 1

Correct any errors in your config.xml file and re-run the script. If no errors are present, the Sitemap Generator will create a new sitemap.xml.gz file in the location you specified in the config file.

5. Submitting your Sitemap to Google

The Sitemap Generator creates a sitemap.xml.gz file in the location you specified in the config file. Once this file is successfully created, make sure it is accessible through a web browser. Then, add it to your Google Sitemaps account. This enables Google to provide you with useful status and statistical information. If Google reports problems with your Sitemap, you can correct the problems and resubmit it. You only have to add the Sitemap manually once. After that, you can use an HTTP request to notify Google about changes to your Sitemap (although you can also resubmit it through your Google webmaster tools account).

6. Setting up a recurring script

We suggest setting up Sitemap Generator to run as often as your content is changed, to a maximum frequency of once per hour.

Webmasters with a UNIX web server may consider setting this up as a cron job.

Webmasters using other platforms should contact their system administrator for help in configuring recurring scripts. You may also benefit from peer advice in the Google Sitemaps Group on Google Groups.

You can use an HTTP request to let Google know about changes to your Sitemap. However, please make sure that you log in to Google webmaster tools with your Google Account once to manually add your Sitemap to your Google webmaster tools account.

Troubleshooting

In this section we talk about some common questions or issues that some people run into while using Sitemap Generator, and what you can do if you come across one of these.

Web-accessible

Issue: Sitemap Generator returns the following error and warning:

	 	[ERROR] When attempting to access your generated Sitemap at the following URL: 	http://www.example.com/sitemap.xml.gz 	we failed to read it.  Please verify the store_into path you specified in 	your configuration file is web-accessible.  Consult the FAQ for more 	information. 	[WARNING] Proceeding to notify with an unverifiable URL.

What just happened? Sitemap Generator created the file where you specified, then attempted to retrieve it using HTTP just as a search engine would, and failed. It went ahead and notified search engines anyway, but it's outputting the error and warning to let you know that your Sitemap may be not readable by search engines.

Sitemap Generator creates your Sitemap file at the path specified in the store_into attribute of your config.xml file. Sitemap Generator then builds a URL to that file using the base_url attribute, and reports the URL to search engines. For instance, if you set the configuration to:

	<site base_url="http://www.example.com/" 	      store_into="/var/www/html/sitemap.xml.gz">

Sitemap Generator will notify search engines to look for your Sitemap at:

	http://www.example.com/sitemap.xml.gz

The file must be accessible through this URL. If the file can not be retrieved using this URL, search engines have no way of finding your Sitemap.

What can you do? You need to verify that your config.xml is specifying the correct base_url and store_into paths for your Sitemap. You also need to confirm that web browsers can retrieve the Sitemap file off of the base_url. If you find errors in the path or URL, you may need to re-run Sitemap Generator, or just move the Sitemap file to the correct place and notify search engines manually through their web sites.

Support for XML

Issue: Sitemap Generator gives the following error:

	 	Some installs of Python 2.2 do not include complete support for XML.  	Please try upgrading your version of Python and re-running the script.

What just happened? As the message says, some platforms have a version of Python (the language the Sitemap Generator script is written in) that is missing support libraries needed for processing XML files. This script requires full XML support in order to run.

What can you do? Try upgrading your installed version of Python to a newer version. You will probably need to contact your system administrator to do this.

Note that this just affects the Sitemap Generator, not Sitemaps overall. If you have another method or tool for creating Sitemaps, you can certainly use it and submit your Sitemaps to search engines.

What are all the extra files in the .gz or .zip?

When you extract the sitemap_gen.py script, you'll probably see quite a few more files than we refer to above. The full file list looks closer to this:

	 	AUTHORS 	ChangeLog 	COPYING 	example_config.xml 	example_urllist.txt 	PKG-INFO 	README 	setup.py 	sitemap_gen.py 	test_sitemap_gen.py

The extra files tend to be information on the package and licensing terms. You are encouraged to look through these files.

The one exception is test_sitemap_gen.py, which is a unit-test script that other developers may find useful if they wish to contribute to this open source project. If you intend to use Sitemap Generator without modifying any of the source code - this is the expected case for nearly everyone - you probably don't need this test script.

If you are interested in helping with this project, please visit http://sourceforge.net/projects/goog-sitemapgen. You can also find links to some third party programs that support Google Sitemaps here.

Non-ASCII characters

Issue: Your site domain name or URLs within it contain non-ASCII characters.

Generally, non-ASCII URLs should be encoded using UTF-8 before being percent-escaped. However, some webservers only respond correctly if URLs are encoded using an encoding other than UTF-8. All URLs within your Sitemap, as well as the URL of the Sitemap itself must be encoded for readability by the web server on which they are located. Within the site definition section, use the optional default_encoding attribute to specify the encoding used by your webserver. If you don't use this tag and your webserver uses an encoding other than UTF-8, we can't know which encoding to use.

If your URLs contain non-ASCII characters, we recommend that you run the Sitemap Generator script using Python 2.3 or higher. This version of Python has increased non-ASCII support. If your domain name contains non-ASCII characters, you must use Python 2.3 or later, as Internationalizing Domain Names in Applications (IDNA) support wasn't added until this version. Without IDNA support, the Sitemap Generator can't correctly encode a non-ASCII domain name.

Last modified: 15 April 2006

How do I add my site to Google's search results?

2007-08-12T00:13:00.001+10:00

http://www.google.com/support/webmasters/bin/answer.py?answer=34397&ctx=sibling

Webmaster Help Center	Change Language:
Google Help > Help Center Home > My site and Google > My site in the Google index

Documentation

Webmaster Guidelines

How do I add my site?

About Google webmaster tools

Webmaster Central

Tools

Google webmaster tools

Submit your content to Google

Google services and tools

How do I add my site to Google's search results?

Inclusion in Google's search results is free and easy; you don't even need to submit your site to Google. Google is a fully automated search engine that uses software known as "spiders" to crawl the web on a regular basis and find sites to add to our index. In fact, the vast majority of sites listed in our results aren't manually submitted for inclusion, but found and added automatically when our spiders crawl the web.

To determine whether your site is currently included in Google's index, just perform a search for your site's URL. For example, a search for [ site:www.google.com ] returns the following results: http://www.google.com/search?hl=en&q=site%3Awww.google.com+

Although Google crawls billions of pages, it's inevitable that some sites will be missed. When our spiders miss a site, it's frequently for one of the following reasons:

The site isn't well connected through multiple links to other sites on the web.
The site launched after Google's most recent crawl was completed.
The design of the site makes it difficult for Google to effectively crawl its content.
The site was temporarily unavailable when we tried to crawl it or we received an error when we tried to crawl it. You can use Google webmaster tools to see if we received errors when trying to crawl your site.

Our intent is to represent the content of the internet fairly and accurately. To help make this goal a reality, we offer guidelines as well as tips for building a crawler-friendly site. While there's no guarantee that our spiders will find a particular site, following these guidelines should increase your site's chances of showing up in our search results.

Consider creating and submitting a detailed site map of your pages. Google Sitemaps is an easy way for you to submit all your URLs to the Google index and get detailed reports about the visibility of your pages on Google. With Google Sitemaps, you can automatically keep us informed of all of your current pages and any updates you make to those pages. Please note that submitting a Sitemap doesn't guarantee that all pages of your site will be crawled or included in our search results.

You may also be interested in...

Was this information helpful?

Search Help Center

How can I create a Google-friendly site?

2007-08-12T00:12:00.002+10:00

http://www.google.com/support/webmasters/bin/answer.py?answer=40349

Webmaster Help Center	Change Language:
Google Help > Help Center Home > My site and Google > My site in the Google index

Documentation

Webmaster Guidelines

How do I add my site?

About Google webmaster tools

Webmaster Central

Tools

Google webmaster tools

Submit your content to Google

Google services and tools

How can I create a Google-friendly site?

Things to do

Our webmaster guidelines provide general design, technical, and quality guidelines. Below are more detailed tips for creating a Google-friendly site.

Give visitors the information they're looking for
Provide high-quality content on your pages, especially your homepage. This is the single most important thing to do. If your pages contain useful information, their content will attract many visitors and entice webmasters to link to your site. In creating a helpful, information-rich site, write pages that clearly and accurately describe your topic. Think about the words users would type to find your pages and include those words on your site.

Make sure that other sites link to yours
Links help our crawlers find your site and can give your site greater visibility in our search results. When returning results for a search, Google combines PageRank (our view of a page's importance) with sophisticated text-matching techniques to display pages that are both important and relevant to each search. Google counts the number of votes a page receives as part of its PageRank assessment, interpreting a link from page A to page B as a vote by page A for page B. Votes cast by pages that are themselves "important" weigh more heavily and help to make other pages "important."

Keep in mind that our algorithms can distinguish natural links from unnatural links. Natural links to your site develop as part of the dynamic nature of the web when other sites find your content valuable and think it would be helpful for their visitors. Unnatural links to your site are placed there specifically to make your site look more popular to search engines. Some of these types of links (such as link schemes and doorway pages) are covered in our webmaster guidelines.

Only natural links are useful for the indexing and ranking of your site.

Make your site easily accessible
Build your site with a logical link structure. Every page should be reachable from at least one static text link.

Use a text browser, such as Lynx, to examine your site. Most spiders see your site much as Lynx would. If features such as JavaScript, cookies, session IDs, frames, DHTML, or Macromedia Flash keep you from seeing your entire site in a text browser, then spiders may have trouble crawling it.

Consider creating static copies of dynamic pages. Although the Google index includes dynamic pages, they comprise a small portion of our index. If you suspect that your dynamically generated pages (such as URLs containing question marks) are causing problems for our crawler, you might create static copies of these pages. If you create static copies, don't forget to add your dynamic pages to your robots.txt file to prevent us from treating them as duplicates.

Things to Avoid

Don't fill your page with lists of keywords, attempt to "cloak" pages, or put up "crawler only" pages. If your site contains pages, links, or text that you don't intend visitors to see, Google considers those links and pages deceptive and may ignore your site.

Don't feel obligated to purchase a search engine optimization service. Some companies claim to "guarantee" high ranking for your site in Google's search results. While legitimate consulting firms can improve your site's flow and content, others employ deceptive tactics in an attempt to fool search engines. Be careful; if your domain is affiliated with one of these deceptive services, it could be banned from our index.

Don't use images to display important names, content, or links. Our crawler doesn't recognize text contained in graphics. Use ALT attributes if the main content and keywords on your page can't be formatted in regular HTML.

Don't create multiple copies of a page under different URLs. Many sites offer text-only or printer-friendly versions of pages that contain the same content as the corresponding graphic-rich pages. To ensure that your preferred page is included in our search results, you'll need to block duplicates from our spiders using a robots.txt file. For information about using a robots.txt file, please visit our information on blocking Googlebot .

You may also be interested in...

Was this information helpful?

Search Help Center

Google Webmaster Guidelines

2007-08-12T00:12:00.001+10:00

http://www.google.com/support/webmasters/bin/answer.py?answer=35769

Webmaster Help Center
Change Language:

Google Help > Help Center Home > My site and Google

Documentation

Webmaster Guidelines

How do I add my site?

About Google webmaster tools

Webmaster Central

Tools

Google webmaster tools

Submit your content to Google

Google services and tools

Webmaster Guidelines

Webmaster Guidelines

Following these guidelines will help Google find, index, and rank your site. Even if you choose not to implement any of these suggestions, we strongly encourage you to pay very close attention to the "Quality Guidelines," which outline some of the illicit practices that may lead to a site being removed entirely from the Google index or otherwise penalized. If a site has been penalized, it may no longer show up in results on Google.com or on any of Google's partner sites.

Design, content, and technical guidelines
Quality guidelines

When your site is ready:

Have other relevant sites link to yours.
Submit it to Google at http://www.google.com/addurl.html.
Submit a Sitemap as part of our Google webmaster tools. Google uses your Sitemap to learn about the structure of your site and to increase our coverage of your webpages.
Make sure all the sites that should know about your pages are aware your site is online.
Submit your site to relevant directories such as the Open Directory Project and Yahoo!, as well as to other industry-specific expert sites.

Design and content guidelines

Make a site with a clear hierarchy and text links. Every page should be reachable from at least one static text link.
Offer a site map to your users with links that point to the important parts of your site. If the site map is larger than 100 or so links, you may want to break the site map into separate pages.
Create a useful, information-rich site, and write pages that clearly and accurately describe your content.
Think about the words users would type to find your pages, and make sure that your site actually includes those words within it.
Try to use text instead of images to display important names, content, or links. The Google crawler doesn't recognize text contained in images.
Make sure that your TITLE tags and ALT attributes are descriptive and accurate.
Check for broken links and correct HTML.
If you decide to use dynamic pages (i.e., the URL contains a "?" character), be aware that not every search engine spider crawls dynamic pages as well as static pages. It helps to keep the parameters short and the number of them few.
Keep the links on a given page to a reasonable number (fewer than 100).

Technical guidelines

Use a text browser such as Lynx to examine your site, because most search engine spiders see your site much as Lynx would. If fancy features such as JavaScript, cookies, session IDs, frames, DHTML, or Flash keep you from seeing all of your site in a text browser, then search engine spiders may have trouble crawling your site.
Allow search bots to crawl your sites without session IDs or arguments that track their path through the site. These techniques are useful for tracking individual user behavior, but the access pattern of bots is entirely different. Using these techniques may result in incomplete indexing of your site, as bots may not be able to eliminate URLs that look different but actually point to the same page.
Make sure your web server supports the If-Modified-Since HTTP header. This feature allows your web server to tell Google whether your content has changed since we last crawled your site. Supporting this feature saves you bandwidth and overhead.
Make use of the robots.txt file on your web server. This file tells crawlers which directories can or cannot be crawled. Make sure it's current for your site so that you don't accidentally block the Googlebot crawler. Visit http://www.robotstxt.org/wc/faq.html to learn how to instruct robots when they visit your site. You can test your robots.txt file to make sure you're using it correctly with the robots.txt analysis tool available in Google webmaster tools.
If your company buys a content management system, make sure that the system can export your content so that search engine spiders can crawl your site.
Use robots.txt to prevent crawling of search results pages or other auto-generated pages that don't add much value for users coming from search engines.

Quality guidelines

These quality guidelines cover the most common forms of deceptive or manipulative behavior, but Google may respond negatively to other misleading practices not listed here (e.g. tricking users by registering misspellings of well-known websites). It's not safe to assume that just because a specific deceptive technique isn't included on this page, Google approves of it. Webmasters who spend their energies upholding the spirit of the basic principles will provide a much better user experience and subsequently enjoy better ranking than those who spend their time looking for loopholes they can exploit.

If you believe that another site is abusing Google's quality guidelines, please report that site at https://www.google.com/webmasters/tools/spamreport . Google prefers developing scalable and automated solutions to problems, so we attempt to minimize hand-to-hand spam fighting. The spam reports we receive are used to create scalable algorithms that recognize and block future spam attempts.

Quality guidelines - basic principles

Make pages for users, not for search engines. Don't deceive your users or present different content to search engines than you display to users, which is commonly referred to as "cloaking."
Avoid tricks intended to improve search engine rankings. A good rule of thumb is whether you'd feel comfortable explaining what you've done to a website that competes with you. Another useful test is to ask, "Does this help my users? Would I do this if search engines didn't exist?"
Don't participate in link schemes designed to increase your site's ranking or PageRank. In particular, avoid links to web spammers or "bad neighborhoods" on the web, as your own ranking may be affected adversely by those links.
Don't use unauthorized computer programs to submit pages, check rankings, etc. Such programs consume computing resources and violate our Terms of Service. Google does not recommend the use of products such as WebPosition Gold™ that send automatic or programmatic queries to Google.

Quality guidelines - specific guidelines

Avoid hidden text or hidden links.
Don't use cloaking or sneaky redirects.
Don't send automated queries to Google.
Don't load pages with irrelevant keywords.
Don't create multiple pages, subdomains, or domains with substantially duplicate content.
Don't create pages that install viruses, trojans, or other badware.
Avoid "doorway" pages created just for search engines, or other "cookie cutter" approaches such as affiliate programs with little or no original content.
If your site participates in an affiliate program, make sure that your site adds value. Provide unique and relevant content that gives users a reason to visit your site first.

If you determine that your site doesn't meet these guidelines, you can modify your site so that it does and then submit your site for reconsideration.

You may also be interested in...

How do I add my site to Google's search results?
How can I create a Google-friendly site?

任意版本到SupeSite5.5/X-Space3.0升级图文教程

2007-08-08T15:44:00.001+10:00

http://www.discuz.net/thread-595510-1-1.html

任意版本到SupeSite5.5/X-Space3.0升级图文教程

SupeSite 5.5/X-Space 3.0 即将发布，提前为大家做个规范的升级教程出来，希望能为大家未来的升级带来方便

一．升级前的准备

1．下载 SupeSite 5.5/X-Space 3.0 到本地或服务器上，如图 1 所示：
注：需要注意的是，请下载和您之前版本编码一致的程序包。比如您之前的SupeSite/X-Space是GBK编码的，那么也请下载GBK编码的程序包。

其中：upload 文件夹中的文件为我们所要使用的程序文件；
   其余都为 SupeSite/X-Space 相关帮助文档。

2．关闭论坛，如图 2 所示：

3．登录SupeSite/X-Space站点

登录SupeSite/X-Space站点设置－基本设置－系统设置－页面风格目录：选择default模板，如图 3 所示：

登录SupeSite/X-Space站点设置－基本设置－系统设置－HTML设置：将各个页面的html都设置为不启用，如图 4 所示：

登录SupeSite/X-Space站点设置－基本设置－频道设置－将首页恢复为程序原来默认的首页。务必不要将自己自定义的页面设置为首页。如图 5 所示：

4．备份SupeSite/X-Space数据库和程序文件
（1）数据库备份方法：
独立主机：直接备份数据库目录就可以（注意备份前停止 MySQL 服务）；
虚拟主机：后台备份或使用phpmyadmin都可以；
参考：SupeSite 5.0 搬家图文教程：http://www.discuz.net/thread-484051-1-1.html

本次演示在后台做的备份：（以Discuz!5.5为例演示）
登录论坛后台－系统工具－数据库－资料备份，如图 6 所示，

如果选择"论坛和SupeSite全部数据"，系统将自动开始备份，并且将备份数据存放于论坛 ./forumdata/ backup_XX 目录下，可以将备份数据下载到本地做下备份。

如果选择"自定义备份"，则您可以根据自己的需要进行数据备份，比如只备份SupeSite数据表或者Discuz!和SupeSite数据表都选择备份。备份后的备份数据存放于论坛 ./forumdata/ backup_XX 目录下，可以将备份数据下载到本地做下备份。

后台备份方法可参考下面的教程：
论坛后台备份完全规范：http://www.discuz.net/thread-505428-1-1.html

（2）程序文件备份方法：
1，       自行备份全部程序文件，方便升级出问题了可以恢复回去。
2，       将 config. php 文件和论坛的config.inc.php下载到本地（备份），以方便新的 config. php 对照进行配置

二．升级过程
以上准备工作都做好了之后，我们开始进入升级步骤。

1.  目录整理
首先在 FTP目录下把所有的程序文件及目录全部移动到一个新建的 bak目录中，如图 7 所示：

2．上传 SupeSite5.5/X-Space3.0 程序文件到空间上
将除了install.php以外的SupeSite5.5 /X-Space3.0全部程序文件以二进制方式上传到安装SupeSite的空间目录上。如图 8 所示：

二进制上传设置方法：
http://www.discuz.net/viewthread.php?tid=73393
以 FlashFXP 为例，如图 9 所示：

3．修改config.php
打开config.php进行修改。可以参照之前备份到本地的config.php和论坛的config.inc.php
各参数说明：如图 10 ，11 ，12 ，13所示：
下图箭头指向的都是必须填写的项目，请参照图中说明进行填写。

其中cookiedomain设置方法：
http://www.discuz.net/thread-267908-1-1.html

4．修改下列文件属性777
设置相关的目录属性，以便数据文件可以被程序正确读写。
使用 FTP 软件登录您的服务器，将服务器上以下目录、以及该目录下面的所有文件的属性设置为777，win主机请设置internet来宾帐户可读写属性。如果下面目录中含有您没有的目录，就不用设置了。如图 14 所示：

./attachments
./cache/robot
./cache/tpl
./channel
./channel/*.*
./data
./data/robot
./data/temp
./data/system
./html
./log
./templates/
./templates/default
./templates/default/*.*
./user
./video
./video/*.*

具体文件权限的修改方法见下面的教程：
文件权限修改方法介绍：http://www.discuz.net/viewthread.php?tid=487165

5．上传升级程序
将程序包 ./update/update.php 以二进制方式上传到SupeSite/X-Space程序根目录，如图 15 所示：

6．升级过程
在浏览器中输入SupeSite/X-Space访问域名/update.php开始升级，如图 16 所示：

从上图上点击升级按钮进入下面的页面，数据库结构添加/升级，如图 17 ，18 ， 19 所示：
系统会自动根据您的数据结构情况，列出每一项您需要升级的数据表和字段，升级程序会引导您依次进行每一步升级操作。
系统会自动给您列出您需要升级的操作。您按照从上到小的顺序依次点击操作即可。请保证上一个操作提示成功了再进入下一步操作。
如果您的数据量很大，推荐逐个升级。即从上到下逐个点击上图蓝色部分的链接，等上一个链接提示成功了再点击下一个链接。
如果您的数据量比较小，可以直接点击上图黄色部分的链接一次性将上面列出的项目都升级了。

每一个项目升级完了都会给您弹出这个显示框提示您成功还是失败。如果失败，记得保留出错提示。成功提示如图 20 所示：

数据库结构添加升级完毕后进入下一步，如图 21 所示：

数据库结构处理完毕后进入下一步操作，如图 22 所示：

进行完上面一步后升级就完毕了，如图 23 所示：

三．升级后的操作

1．如果您之前生成过html，建议您将登录ftp，将html目录下全部的文件删除。并登录站点设置－综合管理－HTML静态设置：进行重新开启html或者手工生成html，如图 24 ，25 所示：

2．删除您站点上面的update.php文件，避免被重复升级，造成站点数据损坏，如图 26 所示：

3．将备份到 bak 文件夹里的 attachments，styles，user 三个文件夹拷贝出来覆盖 5.5 的这三个目录，否则附件和个人空间将不能正常显示。

四.  常见错误解答

1.       升级之后首页空白或者出现如下报错提示
File :
D:\internet\www\templates\default\index.html.php
Not found or have no access!
解答：
如果您升级之后出现空白，可能是您在升级之前没有将模板模板设置为default，或者是您没有将站点首页设置为程序默认的首页，而是自己添加了一个首页。
这样，您需要进行下列操作：
1）登录站点设置－频道操作－功能频道设置：将您自定的首页删除，并指定系统默认的综合首页为首页即可。
2）删除cache/tpl目录下的全部文件

2.       升级过程提示超时
报错提示如下：Fatal error: Maximum execution time of 30 seconds exceeded in D:\internet\www\class\db_mysql.class.php on line 61
解答：
说明您的数据量太大，升级过程超时。
建议您逐步升级，不要一次性升级全部数据表。

[ 本帖最后由紫琼于 2007-6-19 10:28 编辑 ]

本帖最近评分记录

试天翼威望 +1 公测版本也这么升级么？ 2007-4-17 17:13
安笛金钱 +10 很详细 2007-4-17 17:09
安笛威望 +10 很详细 2007-4-17 17:09

碰到问题请先搜索，您的问题其他人很可能已经也碰到过并解决了。
没事的时候多去帮助文档区逛逛啊，那里有好东东哦 ^_^

Quickly Convert phpBB to SMF after Installing SMF

2007-08-08T00:50:00.001+10:00

https://support.lunarpages.com/knowledge_bases/article/312

Quickly Convert phpBB to SMF after Installing SMF

How would I convert my phpBB forum to SMF?
It is actually very easy to do. After installing SMF, you will have an autoinstaller for mods and autoupgrader for new versions in the Package Manager directly in the admin area, and Quick Replies are not a mod but part of the default script. If you do not know how to do manual updates for other forums, this one may be a good choice for you.

phpBB portion
If you already have phpBB going, there isn't anything you need to do to get it ready.

SMF portion - Installing SMF (Manual)

1. Install SMF to a different folder than phpBB. Go to http://www.simplemachines.org/download.php and download the lastest full release (it will say something like smf_1-0-5_install.tar.gz not upgrade or update in the filename).

2. Go into cPanel, click on File Manager and click on the folder icon next to public_html folder, then click the "Create New Folder" link toward the top. In this example, our new forum will be called smf .

3. Now click on the folder icon next to the folder name, and click on the link "Upload file(s)" toward the top. Click the browse button, and locate where you downloaded the SMF zipped file, then click the "Upload" button and wait for the screen to refresh (it may take quite a few moments).

4. Click on the uploaded file, then in the upper right click the "Extract File Contents" link. A new screen will open with the extracted contents, but you will not yet see those contents in the folder listing itself. Click out of the new window that opened, and in the window where you were before, click the link "Up one level" then click back on the folder icon next to the smf folder and you will now see all the files and folders (this wasn't visible before because cPanel doesn't refresh after an extraction).

Note: The files may extract with permissions set to 777 and 666. Due to the use of suphp on our servers, these must be changed to 755 and 644 or you will get 500 Internal Server errors. You can select and change many files or folders at a time by using an FTP program.

5. Open a new window in your brower, and now load the page http://yourdomain.com/smf where yourdomain.com is replaced by your domain name and smf is the folder location where you installed the forum.

6. This screen is the forum settings area with the following fields:

Basic Settings
Forum name: Your forum's name here
Forum URL: http://yourdomain.com/smf (should already be filled in correctly)
Gzip Output: checked already, click to test it is working using the "here" link beneath it
Database Sessions: checked already

MySQL Server Settings
MySQL server name: localhost
MySQL username: cpanelusername_dbusername
MySQL password: dbusername's password
MySQL database name: cpanelusername_dbname
MySQL table prefix: smf_

Most of these settings are pre-filled in. You do need to know the MySQL username, password and database name. If you are going to use the same database as phpBB has and do not remember the MySQL username or password, you can find them in File Manager by clicking on config.php in your phpbb forum folder and then click Edit in the upper right corner. You can copy and paste them from there. Or, go into MySQL database section by logging into another Window of cPanel, click on that area, and create a new DB user with a password, then add that user to the MySQL database. You should copy the database name, database user's name and password at that time and then paste into the fields.

Click to Proceed to the next screen.

7. This area you will create your administrator account.

Create Your Account
Your username: Admin username (might want to use the same one as you had on phpBB)
Password: Admin password
Password: Retype admin password
Email Address: Admin email address

MySQL Database Password
Use the same password you did for the password MySQL database user in step 7

Click "Finish"

8. You will receive a congratulations screen, and then you can click on "your newly installed forum" to see the new forum. You should click on the box to delete the install file first to avoid a security warning. Just clicking on the box will delete the file immediately.

10. If you get a security warning now:

MAJOR SECURITY RISK:
You have not removed install.php!

Go into File Manager and the smf folder, then click on the file named install.php. In the upper right, click the "Delete File" link, then click the trashbin icon to clear it out of the trash. Refresh your forum, the warning should disappear.

SMF portion 2 - Converting phpBB to SMF

1. Go to http://www.simplemachines.org/download.php?converters and find the converter called phpbb2_to_smf.php and click on it to download it. Go into File Manager and navigate to your smf folder, click to upload the file similar to how you did for SMF itself.

2. Open a new window in your browser, and go to http://yourdomain.com/smf/phpbb2_to_smf.php where yourdomain.com is your domain name and smf is the folder where you installed smf.

3. The screen will ask for the path to phpbb and smf on your account:

Where are they?
Path to SMF: /home/cpanelusername/public_html/smf
Path to phpBB2: /home/cpanelusername/public_html/phpbb
SMF Database password: MySQL database user's password used above 2 times already

The path will be /home/cpanelusername/public_html/smf where cpanelusername is replaced with your cPanel username and smf is the folder where smf is installed for the Path to SMF field. It is likely this will already be filled in correctly. The same for the Path to phpBB2, however, it would instead be the location of your phpBB forum. The password needs to be the one to your MySQL database user and you should be well aware of what it is as this is the 3rd time you've had to use it :)

Click to "Continue"

4. You will get several success messages. Copy any fails to see if they affect the forum. You should not receive any fails other than perhaps avatar ones.

Check to decide which smilies you want to use and then click "Convert Smilies" button.

5. You should get a success message for their conversion (and if you don't then you can upload or use your own smilies or the default of SMF), then you can decide to convert attachments if you had the attachments mod installed.

Then click the box to delete the converter file immediately and then the "your installation of SMF" link and your SMF should now be running.

------------
The best part of the the conversion script is that you do not lose your phpBB forum at all, so you can test SMF after you convert your forum to see if it is what you want to use. If you do not, then simply remove it. The database will have smf_ as the prefix in your database, and you can drop any tables with smf_ if you decide to not use it.

The time to do each of the above is as follows:

SMF install - 4 minutes
phpBB to SMF conversion - 2 minutes

Be sure to login to the admin area to be sure you can, change settings as necessary in admin, change links on your site to it.

When satisfied, delete your old phpbb forum folder and the tables in the database for phpbb_. Do this as soon as possible to avoid exploitation.

How to locally install Zend Optimizer

2007-08-08T00:48:00.001+10:00

https://support.lunarpages.com/knowledge_bases/article/310

How to locally install Zend Optimizer

I need a higher version of Zend Optimizer than what is installed on the server. How do I locally install Zend Optimizer?
1. Visit http://www.zend.com/downloads to download latest zend optimizer

2. Extract the files in your local computer. You will find a folder called data. Rename the folder to a more specific name such as zendopt (We will use
this name for the rest of this article).

3. Upload the zendopt folder to public_html.

4. Add the following line to public_html/.htaccess:
suPHP_ConfigPath /home/user/public_html

Note: Rename user with your cpanel username

5. Add following lines to php.ini (create the file if it does not exist):

[Zend]
zend_optimizer.optimization_level=15
zend_extension=/home/USERNAME/public_html/zendopt/4_4_x_comp/ZendOptimizer.so
zend_extension_ts=/home/USERNAME/public_html/zendopt/4_4_x_comp/TS/ZendOptimizer.so

Note: replace USERNAME with your cpanel username. Please also replace
4_4_x_comp with whatever php version on your server. Zendopt folder contains several folders such as 4_4_x_comp, 5_1_x_comp, and 5_2_x_comp. Please select the closest to your php server.

6. Confirm the zend optimizer has been upgraded by creating a php file with the following line and browse the file on the internet:

? echo phpinfo(); ?

(Enclose the above line within arrow brackets. Our desk will not let us show that.)

Welcome, Alan Zhang (logout)

Counters

2007-08-08T00:40:00.001+10:00

https://support.lunarpages.com/knowledge_bases/article/96

Counters

How do I create a counter? Can I make it invisible? Do they help?
If you want to know the traffic that is coming to your site and what people are looking at, Analog, Webalizer, and the Raw Access Logs are a better source than counters. Counters only count hits to the page they are located on and will count every access to the page including you viewing your own page while editing and people hitting refresh/reload. They are very inaccurate.

Counters do serve a purpose, however. They can generate interest in a page by showing that many others have looked at it. A very good use of counters is for sites that are broken into separate categories or areas such as image libraries or sites with multiple scripts such as guestbooks, forums, CMS, etc. Counters will tell you which categories/areas are popular and which are not.

Counters may be visible or invisible. Invisible counters are generally linked to another page where they will be visible to the owner of the site only.

You can create a page hit counter in Cpanel under CGI Center. Click on Counter. Select your settings. Be sure to set Max Digits and Style. Type a name into the Counter Name box. It must be a unique name for each counter and while it is stored as a .dat file, you do not need to type in the .dat part. Click on Preview to see how it will look. Make any changes you wish and Preview them until you are satisfied. Click on Make HTML. Copy the code and paste it into your page in HTML/Code mode. It will look like:

img src="/cgi-sys/Count.cgi?df=somename.dat|display=Counter|ft=6|md=5|frgb=100;139;216|dd=Q"

Once you have the counter in your pages, you may edit the code to do some other nifty things.

To add the comma to separate thousands, add comma=T:

img src="/cgi-sys/Count.cgi?df=somename.dat|display=Counter|ft=6|md=5|frgb=100;139;216|dd=Q|comma=T"

To make the counter invisible, add sh=F:

img src="/cgi-sys/Count.cgi?df=somename.dat|display=Counter|ft=6|md=5|frgb=100;139;216|dd=Q|comma=T|sh=F"

To see an invisible counter, you will need to create a new HTML page which can be as fancy or as simple as you like. If you will use it to see several invisible counters, use tables and paste the codes into cells with the names of the pages. In each cell, paste the same code as you used for that page, but remove the sh=F or change it to sh=T. You should also add incr=F to keep the counter from incrementing when you view it from this page.

This page will not be linked to your site. Only you will know where it is. You may want to put it in a folder and password protect the folder to keep others away.

Parked vs. Add-on Domain

2007-08-08T00:26:00.001+10:00

https://support.lunarpages.com/knowledge_bases/article/93

Parked vs. Add-on Domain

What is the difference between a parked domain and an add-on domain?
A parked domain is an additional domain that points to main directory of your account. You can park an unlimited number of domains at no cost. A parked domain will resolve to your primary domain name.

Say your primary is abc.com and you park xyz.com

In the address bar if you type xyz.com it will resolve to abc.com but in the address bar you will see xyz.com.

An add on domain allows you to run a separate web site to your primary domain. When you create an add on domain, it makes a folder in your public_html folder and you upload the site content into that folder. So essentially you are running 2 separate sites, separate content, off one account. The Basic and Business plans now come with 10 free addon domains.

Say your primary is abc.com and you create addon domain xyz.com. The addon domain is pointed to the xyz folder under public_html

In the address bar if you type xyz.com it will resolve to the content in the xyz folder and in the address bar you will see xyz.com.

With both the parked and add-on domains, you can create seperate email accounts for each domain name.

Welcome, Alan Zhang (logout)