URL分別用三個List保存，
一個是boring，這個list中的url最后來下載
其他兩個是interesting和average
當搜索到url時檢查是否包含設定為boring的詞，并放入boring中

用戶可設定“深度搜索”：每搜到一個url就放在list的最前面
也可廣度

有些網頁鏈接要特殊處理：

讀取資源代碼：

建立多級目錄：
給一個變量寫doc：（在eclipse中，鼠標置上會顯示）
這種log挺好：（apache log4j） 當下載第一個URL時（一般是網站主頁），如果等待時間過長，那么其他線程要么會認為網站已下載完而結束，要么會在下面標*代碼處拋出NullPointerException, 很少能夠存活下來。


估計可能是線程交叉了，還沒來得及同步就跑到后面去執行getDepth()了。
在nextURL = queue.getNextInQueue();后面加上判斷就OK了:

I had to get obsessed with keyboard shortcuts when using IDEA.
Apparently some of that must have rubbed off, because
lately I've been looking for shortcuts to methods and classes in Eclipse 3.0.

There are two traversal shortcuts I use all the time: Ctrl-O and Ctrl-T.

Ctrl-O shows the methods of the class in the current editor in a popup.
Hit Ctrl-O when the popup is up, and you'll see all the inherited
methods as well. This is incredibly useful, as it allows me to bounce
between methods even when I'm not sure which class is implementing
which method.

Ctrl-T shows the type hierarchy of a selected type in a popup. This is the
complement to Ctrl-O. When I'm sure of what
interface I'm looking at, but I really want to pick a particular implementation
and want to go trawling through that
implementation for a bit, Ctrl-T will show me all the subclasses or
implementors for that type.

There is a third option which I haven't used much. Ctrl-F3 shows the
methods of a selected type in a popup. I can see how this can be useful,
but in practice I have a pretty good idea of which methods are attached
 to which classes and Ctrl-Space fills most of my needs there.

However, I have been missing a couple of things. These are the shortcuts
I just found recently, and are very good for hitting up random files:

Ctrl-E shows a popup list of all the open files.
Ctrl-Shift-T creates a dialog box that you can use to navigate to any class.
Ctrl-Shift-R creates a dialog box that shows any resource in the project
(basically any file.)
Alternately, there's an Eclipse plugin called GotoFile which seems to behave
a little more "IDEAish".

Finally, I found a plugin which actually integrates Eclipse with Windows!
Eclipse Platform Extensions is actually functional and useful, although
you wouldn't guess it by looking at the website. Although it says that
it provides a "System GC" functionality, it actually does far more,
like provide a "Open in Windows Explorer" and
"Open Command Window here" dialog to the Package Explorer.

Installing the help system as an infocenter

You can allow your users to access the help system over the Internet or an intranet, by
installing the infocenter and the documentation plug-ins on a server. Clients view help
by navigating to a URL, and the help system is shown in their web browser. The
infocenter help system can be used both for client applications and for web
applications, either of which can have their help accessed remotely. All features
of help system except infopops and active help are supported.

The infocenter help system allows passing number of options that can be used to
customize various aspects of the infocenter. The following options are supported:

• -eclipsehome eclipseInstallPath - specifies Eclipse installation directory.
  This directory is a parent to "plugins" directory and eclipse executable.
  The option must be provided, when current directory from which infocenter
  is launched, is not the same as Eclipse installation directory.
• -data instanceArea - specifies a path that Eclipse can use to write instance data.
  The value can be an absolute path of a directory, or a path relative to Eclipse
  installation directory. The option must be provided when Eclipse is installed in
  the read only location, or has been customized to override osgi.instance.area
  or osgi.instance.area.default properties.
• -host helpServerHost - specifies host name of the interface that help server
  will use. It overrides host name specified in the application server plugin preferences.
• -port helpServerPort - specifies port number that help server will use. It overrides
  port number specified in the application server plugin preferences.
• -locales localeList - specifies a list of locales that infocenter will recognize and
  provide a customized content for. If the option is not specified, infocenter will
  build navigation, and index documents for each preferred locale of the browsers
  accessing the infocenter. When the option is present, locales from browser
  requests will be matched with locales in the list. If browser preferred locale
  does not exist in the list, but its language part does, it will be used. Subsequently,
  additional browser locales in decreased order of preference will be matched
  against the list. If none of the browser locales (or its language part) matches any
  locale on the list, the client will be served content in the default locale - server
  locale or locale passed with -nl option. For example using options

  -nl en -locales de en es fr it ja ko pt_BR zh_CN zh_TW

  will cause infocenter operating in 10 locales. All other locales will receive content
  for en locale.
• -dir rtl - sets right-to-left rendering direction of help UI in the browser.
• -noexec - indicates that Eclipse executable should not be used. You may need to use
  this option when running on a platform for which Eclipse executable is not available.
• Additionally, most options accepted by Eclipse executable can be passed. They are
  especially useful during debugging and for applying customization to Eclipse.
  For example, passing options

  -vmargs -Xmx256M 

  increases memory available to the infocenter and will allow serving a larger book collection.

Installation/packaging

These steps are for the help system integrator and are not meant to address all the possible scenarios.
 It is assumed that all your documentation is delivered as Eclipse plug-ins and, in general, you are
familiar with the eclipse help system.

1. Download the Eclipse Platform Runtime Binary driver from www.eclipse.org.
2. Install (unzip) the driver in a directory, d:\myApp. This will create an eclipse sub-directory,
   d:\myApp\eclipse that contains the code required for the Eclipse platform
   (which includes the help system).

How to start or stop infocenter from command line

The org.eclipse.help.standalone.Infocenter class has a main method that you can use to
launch infocenter from a command line. The command line arguments syntax is:

-command start | shutdown | [-eclipsehome eclipseInstallPath] 
[-data instanceArea] [-host helpServerHost] [-locales localeList] 
[-port helpServerPort] [-dir rtl] [-noexec] [platform options] 
[-vmargs JavaVMarguments]

To start an infocenter on port 8081 issue a start command by running

java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar 
org.eclipse.help.standalone.Infocenter -command start -eclipsehome 
d:\myApp\eclipse -port 8081

To shut the infocenter down issue a shutdown command by running

java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar 
org.eclipse.help.standalone.Infocenter -command shutdown -eclipsehome 
d:\myApp\eclipse

Using the infocenter

Start the web server. Point a web browser to the path "help" web application running on a port
specified when starting the infocenter.  On the machine the infocenter is installed, this would be
http://localhost:8081/help/.

How to start or stop infocenter from Java

When including infocenter as part of another application, it may be more convenient to start it
and stop using Java APIs instead of using system commands. Follow the steps if it is the case:

1. Make sure d:\myApp\eclipse\plugins\org.eclipse.help.base_3.1.0.jar is on your app classpath.
   The class you use to start, and shut down the infocenter isorg.eclipse.help.standalone.Infocenter.
2. Create an array of String containing options that you want to pass to the infocenter. Typically,
   the eclipsehome and port options are needed.

   String[] options = new String[] { "-eclipsehome", "d:\\myApp\\eclipse" ,
    "-port", "8081" }; 

3. In your application, create an instance of the Help class by passing the options.

   Infocenter infocenter = new Help(options); 

4. To start the help system:

   helpSystem.start();

5. To shut the infocenter down:

   helpSystem.shutdown(); 

Making infocenter available on the web

Eclipse contains a complete infocenter and does not require other server software to run.
However, in unsecure environment like Internet, it is recommended infocenter is not accessed
directly by clients, but is made available through an HTTP server or an application server.
Most servers come with modules or servlets for delegating certain request to other web
resources. For example, one may configure a proxy module of Apache HTTP Server to
redirect requests made to http://mycompany.com/myproduct/infocenter to
http://internalserver:8081/help that runs an infocenter. Adding the lines

LoadModule proxy_module modules/ApacheModuleProxy.dll
ProxyPass /myproduct/infocenter http://internalserver:8081/help
ProxyPassReverse /myproduct/infocenter http://internalserver:8081/help

to conf/httpd.conf file of Apache server running mycompany web site accomplishes this.

Some versions of Apache HTTP server, may contain AddDefaultCharset directive enabled in
configuration file. Remove the directive or replace with

AddDefaultCharset Off

to have browsers display documents using correct character set.

Running multiple instance of infocenter

Multiple instances of infocenter can be run on a machine from one installation. Each started
instance must use its own port and be provided with a workspace, hence -port and -data
options must be specified. The instances can serve documentation from different set of plug-ins,
by providing a valid platform configuration with -configuration option.

If -configuration is not used and configuration directory is shared among multiple infocenter
instances, with overlapping set of locales, it must be ensured that all search indexes are created
by one infocenter instance before another instance is started. Indexes are saved in the configuration
directory, and write access is not synchronized across infocenter processes.

[Optional] Installing a minimal set of plug-ins

The infocenter does not require the entire  Eclipse Platform package. It is possible to run the
infocenter with the following plug-ins (located in the  eclipse\plugins directory):

org.apache.lucene
org.eclipse.core.runtime
org.eclipse.help
org.eclipse.help.appserver
org.eclipse.help.base
org.eclipse.help.webapp
org.eclipse.osgi
org.eclipse.tomcat
org.eclipse.update.configurator


Some documentation plug-ins may have dependencies on other plug-ins, usually by specifying required
plug-ins in their plugin.xml. The dependent plug-ins need to be installed on the infocenter as well.
Additionally, plug-ins that were designed for earlier than 3.0 version of Eclipse implicitly require an org.eclipse.core.runtime.compatibility being present plug-in to work.

Infocenter plug-ins can be updated without restarting the infocenter, using commands explained
in Updating a running infocenter from command line topic. To use this functionality, the minimal
set of plug-ins must include org.eclipse.update.core plug-in.

See Help System Preferences for more information on customizing help system.

Class.forName is excellent
例：
在Log4j里定義一個靜態類構造器，里面放apache log4j的初始代碼。

其他如注冊數據源、界面本地化。。。

Eclipse看代碼是最爽的：
查看類的引用、代碼導航

      調試網頁時出錯，無意中發現出錯頁的源文件中有這樣一段注釋：

<title>404 Not Found</title>
<h1>404 Not Found</h1>
/asfsfdsd.jsp was not found on this server.
<p /><hr />
<small>
Resin 2.0.3 (built Wed Oct 17 10:11:08 PDT 2001)
</small>
</address>

<!--
  -- Unfortunately, Microsoft has added a clever new
  -- "feature" to Internet Explorer.  If the text in
  -- an error's message is "too small", specifically
  -- less than 512 bytes, Internet Explorer returns
  -- its own error message.  Yes, you can turn that
  -- off, but *surprise* it's pretty tricky to find
  -- buried as a switch called "smart error
  -- messages"  That means, of course, that many of
  -- Resin's error messages are censored by default.
  -- And, of course, you'll be shocked to learn that
  -- IIS always returns error messages that are long
  -- enough to make Internet Explorer happy.  The
  -- workaround is pretty simple: pad the error
  -- message with a big comment to push it over the
  -- five hundred and twelve byte minimum.  Of course,
  -- that's exactly what you're reading right now.
  -->

這就叫以牙還牙：凡是用Resin服務器的網站，都不會出現M$的惱人友好信息了。

以前一直沒找到這個選項，以為不可以呢。終于發現工具菜單-->選項里的“播放機設置”欄的第一個復選框就是設置將播放器置于最前端。寫出來怕大家有需要的^_^

源多說明通過你的apt能安裝更多軟件，如果下列鏈接有效，就將它加到你的sources.list (注意順序，將速度最快的放在最前頭，apt會默認用前面的鏈接下載軟件)

deb ftp://ftp.sjtu.edu.cn/sites/archive.ubuntu.com breezy main restricted universe multiverse
deb ftp://ftp.sjtu.edu.cn/sites/archive.ubuntu.com breezy-updates main restricted universe multiverse
deb ftp://ftp.sjtu.edu.cn/sites/archive.ubuntu.com breezy-security main restricted universe multiverse
deb http://archive.ubuntu.org.cn/ubuntu breezy main restricted universe multiverse
deb http://archive.ubuntu.org.cn/ubuntu breezy-updates main restricted universe multiverse
deb http://archive.ubuntu.org.cn/ubuntu breezy-security main restricted universe multiverse
deb http://archive.ubuntu.org.cn/ubuntu-cn breezy main universe multiverse restricted
deb http://archive.ubuntu.org.cn/ubuntu hoary main restricted universe multiverse
deb http://archive.ubuntu.org.cn/ubuntu hoary-security main restricted universe multiverse
deb http://archive.ubuntu.org.cn/ubuntu hoary-updates main restricted universe multiverse
deb http://archive.ubuntu.org.cn/ubuntu-cn ubuntu.org.cn main universe multiverse restricted
deb http://archive.ubuntu.org.cn/ubuntu hoary-backports main universe multiverse restricted
deb http://archive.ubuntu.org.cn/backports hoary-extras main universe multiverse restricted
deb-src http://archive.ubuntu.org.cn/ubuntu hoary main restricted universe multiverse
deb-src http://archive.ubuntu.org.cn/ubuntu hoary-security main restricted universe multiverse
deb-src http://archive.ubuntu.org.cn/ubuntu hoary-updates main restricted universe multiverse
deb http://helix.alioth.debian.org/deb sid main non-free
deb-src http://helix.alioth.debian.org/deb sid main non-free
deb http://ubuntu.cn99.com/ubuntu/ breezy main restricted universe multiverse
deb http://ubuntu.cn99.com/ubuntu/ breezy-updates main restricted universe multiverse
deb http://ubuntu.cn99.com/ubuntu/ breezy-security main restricted universe multiverse
deb http://ubuntu.cn99.com/ubuntu-cn/ breezy main restricted universe multiverse
deb http://ubuntu.cn99.com/backports/ breezy-extras main restricted universe multiverse

Source: http://openide.netbeans.org/tutorial/api-design.html#design.less.friend

Allow access only from a friend code

Another useful technique to not expose too much in API is to give access to certain functionality (e. g. ability to instantiate a class or to call a certain method) just to a friend code.

Java by default restricts the friends of a class to those classes that are in the same package. If there is a functionality that you want share just among classes in the same package, use package-private modifier in definition of a constructor, a field or a method and then it will remain accessible only to friends.

Sometimes however it is more useful to extend the set of friends to a wider range of classes - for example one wants to define a pure API package and put the implementation into separate one. In such cases following trick can be found useful. Imagine there is a class item:

public final class api.Item {
    /** Friend only constructor */
    Item(int value) {
        this.value = value;
    }

    /** API method(s) */
    public int getValue() {
        return value;
    }
        
    /** Friend only method */
    final void addListener(Listener l) {
        // some impl
    }
}

that is part of the API, but cannot be instanitated nor listened on outside of the friend classes (but these classes are not only in api package). Then one can define an Accessor in the non-API package:

public abstract class impl.Accessor {
    public static Accessor DEFAULT;

    static {
        // invokes static initializer of Item.class
        // that will assign value to the DEFAULT field above
        Class c = api.Item.class;
        try {
            Class.forName(c.getName(), true, c.getClassLoader());
        } catch (ClassNotFoundException ex) {
            assert false : ex;
        }
        assert DEFAULT != null : "The DEFAULT field must be initialized";
    }

    /** Accessor to constructor */
    public abstract Item newItem(int value);
    /** Accessor to listener */
    public abstract void addListener(Item item, Listener l);
}

with abstract methods to access all friend functionality of the Item class and with a static field to get the accessor's instance. The main trick is to implement the Accessor by a (non-public) class in the api package:

final class api.AccessorImpl extends impl.Accessor {
    public Item newItem(int value) {
        return new Item(value);
    }
    public void addListener(Item item, Listener l) {
        return item.addListener(l);
    }
}

and register it as the default instance first time somebody touches api.Item by adding a static initializer to the Item class:

public final class Item {
    static {
        impl.Accessor.DEFAULT = new api.AccessorImpl();
    }

    // the rest of the Item class as shown above
}

Then the friend code can use the accessor to invoke the hidden functionality from any package:

api.Item item = impl.Accessor.DEFAULT.newItem(10);
impl.Accessor.DEFAULT.addListener(item, this);

轉自：http://blog.csdn.net/3cts/archive/2005/12/30/566079.aspx 　　引言 　　 　　大家都知道可以通過post或者get獲得form表單的數據，那么我們如何實現不刷新的提交直接獲得頁面上的數據呢？這就要借助xmlhttp協議了。xmlhttp是xmldom技術的一部分。 　　 　　下面的代碼就是一個很簡單的例子，我們利用xmlhttp技術實現簡單的用戶登陸。 　　 　　開始 　　 　　1.簡單的登錄頁面 　　 　　login.jsp 　　function toServer(){ 　　var xml = "<root>"+ 　　"<name>"+document.all('name').value+"</name>"+ 　　"<pwd>"+document.all('pwd').value+"</pwd>"+ 　　"</root>"; 　　 　　var XMLSender = new ActiveXObject("Microsoft.XMLHTTP" ); 　　XMLSender.Open("POST",'do_login.jsp',false); 　　XMLSender.send((xml)); 　　alert(XMLSender.responseText);　//可處理后臺返回的結果 　　} 　　 　　姓名：<input type="text" id="name" /><br> 　　密碼：<input type="text" id="pwd" /><br> 　　<input type="button" value="登錄" onclick="toServer()"> 　　 　　2.后臺的登錄處理頁面 　　do_login.jsp 　　 　　<% 　　//讀取XMLHTTP流 　　java.io.BufferedReader br =　request.getReader(); 　　String str = ""; 　　while (str != null) { 　　str = br.readLine(); 　　process (str); //可通過任何語言實現解析XML，進行業務處理 　　} 　　 　　//返回信息 　　javax.servlet.ServletOutputStream sos = response.getOutputStream(); 　　sos.print("login success" ); 　　sos.close(); 　　%> 　　與傳統的“提交－回發－重繪”式的web系統基本運行結構不同，我們可以通過通過XMLHTTP實現無刷新的客戶端直接與服務器交互，極大的提高用戶的感受度。 　　 　　查考資料 　　 　　XMLHTTP方法： 　　 　　Open bstrMethod, bstrUrl, varAsync, bstrUser, bstrPassword 　　bstrMethod：數據傳送方式，即GET或POST。 　　bstrUrl：服務網頁的URL。 　　varAsync：是否同步執行。缺省為True，即同步執行，但只能在DOM中實施同步執行。 　　應用中一般將其置為False，即異步執行。 　　bstrUser：用戶名，可省略。 　　bstrPassword：用戶口令，可省略。 　　 　　Send varBody 　　varBody：指令集。可以是XML格式數據，也可以是字符串，流，或者一個無符號整數數組。也可以省略，讓指令通過Open方法的URL參數代入。 　　 　　setRequestHeader bstrHeader, bstrValue 　　bstrHeader：HTTP 頭(header) 　　bstrValue：HTTP 頭(header)的值 　　如果Open方法定義為POST，可以定義表單方式上傳： 　　xmlhttp.setRequestHeader "Content-Type", "application/x-www-form-urlencoded" 　　 　　XMLHTTP屬性： 　　 　　onreadystatechange：在同步執行方式下獲得返回結果的事件句柄。只能在DOM中調用。 　　responseBody：結果返回為無符號整數數組。 　　responseStream：結果返回為IStream流。 　　responseText ：結果返回為字符串。 　　responseXML：結果返回為XML格式數據。

By: Dion Hinchcliffe

• Content with Style: Fixing the Back Button and Enabling Bookmarking for AJAX Apps - Mike Stenhouse explains how to fix two of the more distracting problems with Ajax. These can be particularly problematic for users new to Ajax applications.  Since Ajax apps typically load into a single web page, it makes pressing the Back button meaningless or actually harmful.  And this breaks the browser usage model annoyingly.  Also, individual views of data in an Ajax application cannot have a URL or permalinks unless precautions are taken.  Mike does a great job covering how to reduce these problems.
  
• Saving Session Across Page Loads Without Cookies, On The Client Side - Ajax virtuoso Brad Neuberg strikes again with a detailed explanation of how to deal with saving session information across page loads without relying on cookies.  This is important in larger applications which typically want to store more information than a cookie can hold.  Brad also has some terrific tools to deal with this as well (see AMASS below)
  
• Call SOAP Web services with AJAX - By design, Ajax is a voracious consumer of web services like XML/HTTP, REST, and SOAP.  A great article at IBM's DeveloperWorks describes how to easily call SOAP web services from Ajax.  This is important because SOAP is a complex protocol that requires some familiarity to use.  While Ajax development tools like Atlas, General Interface, and Bindows will solve this by providing a SOAP stack, for many, hand development of back-end SOAP request is the only option right now to achieve interoperability with WS-I Basic Profile web services.
  
• Ajax using only an image - Browsers and networks continue to get more secure and many configurations will not allow an Ajax application to use web services, and almost none of them will allow you to access a server other than the one the Ajax app loaded from.  Enter an elegant technique to solve this by using image URLs.  Not for the faint of heart, and certainly a possible security hole but a compelling solution nonetheless.
  

Ajax Tools and Libraries

• - I've not used this Ajax development environment extensively yet but it apparently eats its own dog food and runs entirely inside a browser (which apparently must be Internet Explorer).  Supposedly containing an entire SOAP stack, a full-blown IDE, and numerous libraries, General Interface is one of the leading solutions in this space and can be downloaded and used today.  TIBCO cautions you not to use it for production apps yet, but my initial use was encouraging.
  
• Microsoft Atlas - A serious contender in the Ajax IDE space (details here), Microsoft is planning for Atlas to be a heavy-duty, enterprise scale Ajax solution.  Integrated into Visual Studio 2005, Atlas is just a code name but expect that it will be a leading Ajax player from the get go and will live up to its name.
  
• Dojo - Still in early release, the open source Ajax library, Dojo, is getting lots of attention from folks in the know.  Dojo is billed as a "powerful, portable, lightweight, and tested tools for constructing dynamic interfaces. Dojo lets you prototype interactive widgets quickly, animate transitions, and build Ajax requests with the most powerful and easiest to use abstractions available."  I haven't used it yet, but you can bet I will be soon.
  
• Script.aculo.us - One of the very best Ajax visual effects libraries that I've used is the eponymous script.aculo.us.  Advertised as "Web 2.0 JavaScript", script.aculo.us has numerous effects and convenience tools, all built on nice, tight object-oriented abstractions.  I've used it and I can recommend it for its simplicity and reliability.
  
• Bindows - Mind-blowing Ajax library for recreating the full richness of native applications, and includes a SOAP stack.
  
• AMASS - Ajax gets good client-side storage.  A brilliant piece of work by Brad Neuberg, check out a description of how AMASS works here.
  
• TrimQuery - A robust JavaScript database for Ajax.  When combined with AMASS above, neat things can really happen.
  
  
  
  
  
  
• Ruby on Rails - Should probably be listed first, not down here.  The best lightweight, server-side Ajax framework out there today.  Note that Ajax pioneers and Web 2.0 leaders 37Signals sponsor this site and RoR is used by a great many successful Web 2.0 sites.
  
  
• Log4Ajax - Many serious developers wouldn't switch to a new programming model without a Log4J equivalent and here it is.  Both traditional console as well as advanced logging support for Ajax is here today.  SourceForge site here.
  
• Backbase - This IDE is getting good reviews but it apparently uses an abstraction layer like Morfik.  I haven't used it yet but I keep hearing about it.
  
• Sajax - A good competent server-side framework featuring support for most common back-end languages like Perl, Python, Ruby and much more.
  

Note: The most complete Ajax framework listing I've seen available is here.

Ajax News and Resources

• The Ajax Developer's Journal - Good sources of news for Ajax are still pretty scarce but that's starting to change in a big way.  SYS-CON has recently launched their Ajax Developer's Journal and has been working closely with Jesse James Garrett, who coined the term.  Expect lots of interesting and topical new articles and coverage on a regular basis.
  
• Ajaxian - Dion Almaer and Ben Galbraith have been working on Ajaxian for a while now and it remains one of the very best sources for the latest Ajax news, tools, events, and general inspiration.
  

Critiques and Analysis of Ajax

• Ajax Mistakes - This is Alex Bosworth's terrific analysis of the early problems with Ajax.  He a big believer in the technology and his Ajax-powered LiveMarks site is one of my absolute favorites.  A good place to start to understand some of the challenges with Ajax.
  
• Fixing Ajax: XmlHttpRequest Considered Harmful - Some good coverage of why Ajax doesn't really enable the use of the services of other web sites without a lot of work.  This is a big barrier to leveraging Web 2.0's global services landscape.  This can be solved a number of ways however and the options are explored here.  The image URL solution a few paragraphs above is missing but otherwise this is an excellent summary.
  
  
  
  
  
  
• 10 Places You Must Use Ajax - Alex is back and carefully enumerates the good places to use Ajax.  He also covers when to avoid it.  Excellent material for those learning how to design with Ajax.
  
• Top 10 Reasons Ajax Is Here To Stay - Andre Charland nails it.  Though some folks dislike Ajax for a variety of reasons, here are some terrific positive motivations for using it today.
  

posted Friday, 30 December 2005