在网上找?jin)很久才扑ֈdeveloperWorks上的一个解x案：(x)
在命令提C符里切换到目录“C:\Program Files\IBM\SDP70\jdk\jre\bin”Q运?#8220;java.exe -Xshareclasses:destroyAll”
q样p正常启动RAD?jin)?/strong>
原因描述如下Q?/p>
Q摘录自http://www-1.ibm.com/support/docview.wss?uid=swg21281393Qƈ通过Google Translate转译Q译文已作修改）(j)
×××××××××××××××××××××××××××××××××××××
问题Q摘要）(j)
此说明解释如何解决错?#8220;JVM的终止。退Z? 1”?br />
起因
RAD自带的IBM JVM使用?jin)一个高速缓存参数来提高性能。而因为JVM的崩溃，比如蓝屏Q或断电(sh)Q都可能造成Java高速缓存被损坏?而JVM?x)拒l连接到一个损坏的高速缓存?/p>
解决问题
要解册个问题，使用“-Xshareclasses:destroyAll”的Java选项销毁所有的׃nU缓存。这是一U实用工具选项Q所以不?x)启动JVM 。如果?zhn)惌q么做，只要从命令提C符使用参数“-Xshareclasses:destroyAll”来运行RAD使用的java?/p>
××××××××××××××××××××××××××××××××××××××
]]>
从一大堆q中找出可以理解的信息Q字母）(j)
Java解决Ҏ(gu)Q?br />
public class Test {
public static void main(String[] args) throws Exception {
URL url = new URL("http://www.pythonchallenge.com"
+ "/pc/def/ocr.html");
BufferedReader reader = new BufferedReader(new
InputStreamReader(url.openStream()));
StringBuffer sb = new StringBuffer();
int i = reader.read();
while(i != -1)
{
if((i >= (int)'A' && i <= (int)'Z')
|| (i >= (int)'a' && i <= (int)'z'))
{
sb.append((char)i);
}
i = reader.read();
}
reader.close();
String source = sb.toString();
//面源码中最后一个单词是below
System.out.println(
source.substring(source.indexOf("below") + 5)
);
}
}
public static void main(String[] args) throws Exception {
URL url = new URL("http://www.pythonchallenge.com"
+ "/pc/def/ocr.html");
BufferedReader reader = new BufferedReader(new
InputStreamReader(url.openStream()));
StringBuffer sb = new StringBuffer();
int i = reader.read();
while(i != -1)
{
if((i >= (int)'A' && i <= (int)'Z')
|| (i >= (int)'a' && i <= (int)'z'))
{
sb.append((char)i);
}
i = reader.read();
}
reader.close();
String source = sb.toString();
//面源码中最后一个单词是below
System.out.println(
source.substring(source.indexOf("below") + 5)
);
}
}
附Python和ShellQ?br />
Python:
>>> text = """
<copy and paste>
"""
>>> import string
>>> for i in text:
if i in string.ascii_letters:
print i,
<copy and paste>
"""
>>> import string
>>> for i in text:
if i in string.ascii_letters:
print i,
Shell:
$ curl http://www.pythonchallenge.com/pc/def/ocr.html | grep -o [a-z]
]]>
Java解决Ҏ(gu)Q?
1 public class Test {
2 public static void main(String[] args) {
3 String a = "g fmnc wms bgblr rpylqjyrc gr zw fylb. rfyrq "
+ "ufyr amknsrcpq ypc dmp. bmgle gr gl zw fylb "
+ "gq glcddgagclr ylb rfyr'q ufw rfgq rcvr gq "
+ "qm jmle. sqgle qrpgle.kyicrpylq() gq pcamkkclbcb. "
+ "lmu ynnjw ml rfc spj.";
4 char[] ac = a.toCharArray();
5 int zi = (int)'z';
6 int ai = (int)'a';
7 for(int index=0; index<ac.length; index++)
8 {
9 int aci = (int)ac[index];
10 if(aci >= ai && aci <= zi)
11 {
12 int aci2 = (int)ac[index] + 2;
13
14 System.out.print((char)((aci2>zi)?(aci2%(zi+1)+ai):aci2));
15 }
16 else
17 {
18 System.out.print((char)aci);
19 }
20 }
21 }
22 }
2 public static void main(String[] args) {
3 String a = "g fmnc wms bgblr rpylqjyrc gr zw fylb. rfyrq "
+ "ufyr amknsrcpq ypc dmp. bmgle gr gl zw fylb "
+ "gq glcddgagclr ylb rfyr'q ufw rfgq rcvr gq "
+ "qm jmle. sqgle qrpgle.kyicrpylq() gq pcamkkclbcb. "
+ "lmu ynnjw ml rfc spj.";
4 char[] ac = a.toCharArray();
5 int zi = (int)'z';
6 int ai = (int)'a';
7 for(int index=0; index<ac.length; index++)
8 {
9 int aci = (int)ac[index];
10 if(aci >= ai && aci <= zi)
11 {
12 int aci2 = (int)ac[index] + 2;
13
14 System.out.print((char)((aci2>zi)?(aci2%(zi+1)+ai):aci2));
15 }
16 else
17 {
18 System.out.print((char)aci);
19 }
20 }
21 }
22 }
附上Python和Shell解决Ҏ(gu)Q?br />
Python:
1 >>> import string
2 >>> text = """g fmnc wms bgblr rpylqjyrc gr zw fylb. rfyrq ufyr
3 amknsrcpq ypc dmp. bmgle gr gl zw fylb gq glcddgagclr ylb rfyr'q
4 ufw rfgq rcvr gq qm jmle. sqgle qrpgle.kyicrpylq() gq pcamkkclbcb.
5 lmu ynnjw ml rfc spj."""
6 >>> table = string.maketrans(
7 string.ascii_lowercase,
8 string.ascii_lowercase[2:]+string.ascii_lowercase[:2])
2 >>> text = """g fmnc wms bgblr rpylqjyrc gr zw fylb. rfyrq ufyr
3 amknsrcpq ypc dmp. bmgle gr gl zw fylb gq glcddgagclr ylb rfyr'q
4 ufw rfgq rcvr gq qm jmle. sqgle qrpgle.kyicrpylq() gq pcamkkclbcb.
5 lmu ynnjw ml rfc spj."""
6 >>> table = string.maketrans(
7 string.ascii_lowercase,
8 string.ascii_lowercase[2:]+string.ascii_lowercase[:2])
Shell:
$ tr [a-z] [c-za-b]
]]>
]]>
Ҏ(gu)Q含一大口_(d)口分多ơ吞下，直至不打嗝?Q一般两大口水量可以搞定）(j)
PS: 代码实现Q?br>
while(打嗝)
{
for(int index=0; index<2; index++)
{
含一大口_(d)
whileQ口中还有水Q?br> {
吞一口Q?br> no sleepQ?br> }
no sleepQ?br> }
sleep 5U；
}
{
for(int index=0; index<2; index++)
{
含一大口_(d)
whileQ口中还有水Q?br> {
吞一口Q?br> no sleepQ?br> }
no sleepQ?br> }
sleep 5U；
}
]]>
1、jsp:usebean标签中， 若引用的bean不存在，?x)自动调用默认构造器生成一个javabean实例Q所以不要在servlet里再用session.getAttribute来判断bean是否为空Q因定不为空Q，应该判断里面的字D|否ؓ(f)null或ؓ(f)初始化状态?/p>
2、jsp:usebean 的class属性应该是cȝ全名Q包括包名）(j)。在前面<%@ import>中import的包Q在tag里不起作用，只对jsp里面的java代码有用Q所以tag里要使用cȝ全名
3、post时如果表单里有中文，?x)出C文ؕ码，在servlet里调用request.getParameter之前执行request.setCharacterEncoding("gb2312");可以正识别和昄中文?jin)?br />
如果是url中用中文参数Q如someaction.jsp?q=中文问题Q则要加一个filter来setEncodingQ因为post和get传送参数的处理方式不一栗url中包含中文参数的讄参考：(x)http://www.itet.cn/0512456328001529/JSP/0691214511318687.html
]]>
]]>
String sql
=
"
select s.name from student s where s.id='
"
+
sId
+
"
'
"Q?/span>
后来我开始?strong>PreparedStatementQ在SQL里用“？”标记参敎ͼ然后用setXXXҎ(gu)l参数赋倹{当时只知道q样用是因ؓ(f)?strong>setDateQsetTimeStampq些用?”连接不能直接嵌入的倹{?br />
感觉PreparedStatement?strong>性能斚w应该也能快点Q可能DBMS?x)重用，但不明底层原理?br />
q次《数据库实现》课E终于让我弄懂了(jin)Q?strong>每个SQL语句都要通过 语法分析 -> 生成逻辑查询计划 -> 逻辑优化 -> 物理优化 {步骤生成具体的执行计划Q用PreparedStatement可以生成一个执行计划，以后只是参数改变Q相当于执行计划?strong>执行环境改变Q，前面的四个步骤也?strong>省略Q从而提高了(jin)效率?br />
如果一个SQL语句要被反复多次执行Q或多用户同时操作，则应选用PreparedStatementQ?/p>
]]>
]]>
如下代码所C：(x)
//接收到的数据存到字节数larrayint firstChar = inputStream.read();int length = inputStream.available();byte[] array = new byte[length+1];array[0] = (byte)firstChar;inputStream.read(array,1,length);]]>
最后作者以StrutsZQ介l了(jin)几种选择Ajax的场景：(x)
1 现有的Struts应用E序要用AjaxQ请使用AjaxAnywhere
2 建立新的应用E序准备使用AjaxQ参考AppfuseQ它集成?jin)DWR的Ajax
3 中期目标Q?使用一U支持Ajax的JSF的实玎ͼMyFaces或者Struts Shale
原文地址Q?A >http://blog.csdn.net/danny_xcz/archive/2006/03/03/614302.aspx
]]>
步骤Q?BR>
1、在应用E序文g根目录下新徏一个META-INF目录Q在该目录下新徏MANIFEST.MF文gQ?
文g内容为：(x)
1 Main-Class: 包名.ȝ?nbsp;
2
3
2
3
2、将应用E序根目录下所有文件用winrar或winzip打包Q格式ؓ(f)zipQ?
3、将zip文g扩展名改为jar Q?BR>
4、双击jar文g卛_q行?
希望能对大家有点帮助?img src ="http://www.aygfsteel.com/Andyluo/aggbug/31057.html" width = "1" height = "1" />
]]>
]]>
lg?/a>
cd
?jin)解l构?jin)就开始看吧，go
]]>
Class.forName("weblech.util.Log4j");
其他如注册数据源、界面本地化。。?BR>
Eclipse看代码是最爽的Q?BR>查看cȝ引用、代码导?img src ="http://www.aygfsteel.com/Andyluo/aggbug/31010.html" width = "1" height = "1" />
]]>
If you were going to provide some quick basic guidelines for designing rich applications what would they be?
By: Bill Scott
Jan. 7, 2006 02:30 PM
Source: Nine Tips for Designing Rich Internet Applications
*****************************************************************
Recently I was asked to provide input into a presentation. The question was asked, if you were going to provide some quick basic guidelines for designing rich applications what would they be.
Here were the nine thoughts as they originally came to my head.
1) Make it directly interactive
Instead of page to page interactions think direct interaction. Use in context editing as much as possible. Use drag and drop only where it makes sense. Barring a selection model, put tools as close to the objects being edited as possible. Cooper states it as "Where there is output, let there be input."
2) Make it inviting
Use hover to invite users to the next level of interaction. If the interface responds well to light events (like hover) it can be used to entice the user to interact.
3) Use lightweight, in-context popups instead of page transitions where possible
Although they will eventually get over-used, lightweight popups can be your friend. Think of them as annexed areas for your page.
4) Use real-estate creatively
As mentioned popups help. But slide outs have long been allies in desktop tools, they can be an aid in the world of the web.
5) Cross page boundaries reluctantly
Think of a page switch as a context boundary that the user may or may not want to cross. Think of it as a place that many of your users will lose interest and no longer follow you.
6) Create a light footprint
Make it extremely easy to interact. Rating movies or news with just a click on a star with no-refresh is awesome. Checking hostnames without leaving the page is an excellent way to keep a user engaged. Shopping by clicks that only add to a container on the page (instead of going to a new page) are like impulse aisles in the grocery store.
7) Think of your interactions as storyboards
As the designer you are the director. Think about the event states as acts in a play and your interface elements as actors. Get them all moving towards telling your story. Putting the frames down on a storyboard is a great way to rehearse your script. Think of the interesting moments as opportunities for engagement.
8) Communicate transitions
Keeping the user informed during lightweight operations (that don't leave the page) with spinning wheels, busy or progress indicators keep the user engaged with a living page.
9) Think in objects
Instead of thinking about content and pages, think about Rich Internet Objects. The travel log in Yahoo!'s Trip Planner is a good example. Once created it can be searched for or shared. This will help you create more interactive applications and make the user's work recognizable and sharable.
These are not exhaustive. Even as I go to publish this I can think of other tips to include... but I will resist adding to the list. Perhaps you have some tips/principles that have helped you solve design challenges?
Source: Nine Tips for Designing Rich Internet Applications
*****************************************************************
Recently I was asked to provide input into a presentation. The question was asked, if you were going to provide some quick basic guidelines for designing rich applications what would they be.
Here were the nine thoughts as they originally came to my head.
1) Make it directly interactive
Instead of page to page interactions think direct interaction. Use in context editing as much as possible. Use drag and drop only where it makes sense. Barring a selection model, put tools as close to the objects being edited as possible. Cooper states it as "Where there is output, let there be input."
2) Make it inviting
Use hover to invite users to the next level of interaction. If the interface responds well to light events (like hover) it can be used to entice the user to interact.
3) Use lightweight, in-context popups instead of page transitions where possible
Although they will eventually get over-used, lightweight popups can be your friend. Think of them as annexed areas for your page.
4) Use real-estate creatively
As mentioned popups help. But slide outs have long been allies in desktop tools, they can be an aid in the world of the web.
5) Cross page boundaries reluctantly
Think of a page switch as a context boundary that the user may or may not want to cross. Think of it as a place that many of your users will lose interest and no longer follow you.
6) Create a light footprint
Make it extremely easy to interact. Rating movies or news with just a click on a star with no-refresh is awesome. Checking hostnames without leaving the page is an excellent way to keep a user engaged. Shopping by clicks that only add to a container on the page (instead of going to a new page) are like impulse aisles in the grocery store.
7) Think of your interactions as storyboards
As the designer you are the director. Think about the event states as acts in a play and your interface elements as actors. Get them all moving towards telling your story. Putting the frames down on a storyboard is a great way to rehearse your script. Think of the interesting moments as opportunities for engagement.
8) Communicate transitions
Keeping the user informed during lightweight operations (that don't leave the page) with spinning wheels, busy or progress indicators keep the user engaged with a living page.
9) Think in objects
Instead of thinking about content and pages, think about Rich Internet Objects. The travel log in Yahoo!'s Trip Planner is a good example. Once created it can be searched for or shared. This will help you create more interactive applications and make the user's work recognizable and sharable.
These are not exhaustive. Even as I go to publish this I can think of other tips to include... but I will resist adding to the list. Perhaps you have some tips/principles that have helped you solve design challenges?
]]>
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 afriendcode.
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
friendfunctionality 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);
]]>
引言
大家都知道可以通过post或者get获得form表单的数据，那么我们如何实现不刷新的提交直接获得面上的数据呢？q就要借助xmlhttp协议?jin)。xmlhttp是xmldom技术的一部分?BR>
下面的代码就是一个很单的例子Q我们利用xmlhttp技术实现简单的用户登陆?BR>
开?/B>
1.单的d面
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); //可处理后台返回的l果
}
姓名Q?lt;input type="text" id="name" /><br>
密码Q?lt;input type="text" id="pwd" /><br>
<input type="button" value="d" onclick="toServer()">
2.后台的登录处理页?BR> do_login.jsp
<%
//dXMLHTTP?BR> java.io.BufferedReader br = request.getReader();
String str = "";
while (str != null) {
str = br.readLine();
process (str); //可通过M语言实现解析XMLQ进行业务处?BR> }
//q回信息
javax.servlet.ServletOutputStream sos = response.getOutputStream();
sos.print("login success" );
sos.close();
%>
与传l的“提交－回发Q重l”式的webpȝ基本q行l构不同Q我们可以通过通过XMLHTTP实现无刷新的客户端直接与服务器交互，极大的提高用L(fng)感受度?BR>
查考资?/B>
XMLHTTPҎ(gu)Q?BR>
Open bstrMethod, bstrUrl, varAsync, bstrUser, bstrPassword
bstrMethodQ数据传送方式，即GET或POST?BR> bstrUrlQ服务网늚URL?BR> varAsyncQ是否同步执行。缺省ؓ(f)TrueQ即同步执行Q但只能在DOM中实施同步执行?BR> 应用中一般将其置为FalseQ即异步执行?BR> bstrUserQ用户名Q可省略?BR> bstrPasswordQ用户口令，可省略?BR>
Send varBody
varBodyQ指令集。可以是XML格式数据Q也可以是字W串Q流Q或者一个无W号整数数组。也可以省略Q让指o(h)通过OpenҎ(gu)的URL参数代入?BR>
setRequestHeader bstrHeader, bstrValue
bstrHeaderQHTTP ?header)
bstrValueQHTTP ?header)的?BR> 如果OpenҎ(gu)定义为POSTQ可以定义表单方式上传：(x)
xmlhttp.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
XMLHTTP属性：(x)
onreadystatechangeQ在同步执行方式下获得返回结果的事g句柄。只能在DOM中调用?BR> responseBodyQ结果返回ؓ(f)无符h数数l?BR> responseStreamQ结果返回ؓ(f)IStream?BR> responseText Q结果返回ؓ(f)字符丌Ӏ?BR> responseXMLQ结果返回ؓ(f)XML格式数据?/TD>
]]>
By: Dion Hinchcliffe
Dec. 31, 2005 01:30 AM
http://au.sys-con.com/read/166995.htm
Ajax has been the other big software story of 2005, along with Web 2.0. An optional ingredient to Web 2.0 software, Ajax has changed the perception of Web-based software as being horribly clunky, page-oriented, and boring when compared to native computer applications. Ajax describes a set of techniques that makes Web software quite the opposite. A quick visit to Google Maps and its live scrollable map tiles or NetVibes and its drag-and-drop reorganization of your personal data both show how potent and compelling Ajax techniques really are.
I originally covered the current state of Ajax back in August in a widely linked article. It still provides a good summary of the history, benefits, and pitfalls of Ajax but it's amazing what has happened since then. It's also interesting to see what issue haven't been resolved. Though Ajax isn't a technology, it's strictly constrained by the technologies that it uses to describe how to weave visually arresting, highly intereactive, web service-based applications that can be loaded into any browser with a single URL, all without installing any software. But some challenges continue to remain but are decreasing in concern.
The term and world-wide attention behind Ajax is not even a year old, but you can find a wide range of poweful tools either with newly added support for Ajax or created just to support the Ajax way of life. In addition, many of the constaints and problems with Ajax have been resolved or greatly reduced. But keeping track of all these developments is very difficult, so I've compiled a summary here of the major advances in Ajax so far this year.
I hope you enjoy. And as always, please add your own at the bottom for all to benefit...
Improved Ajax Techniques
http://au.sys-con.com/read/166995.htm
Ajax has been the other big software story of 2005, along with Web 2.0. An optional ingredient to Web 2.0 software, Ajax has changed the perception of Web-based software as being horribly clunky, page-oriented, and boring when compared to native computer applications. Ajax describes a set of techniques that makes Web software quite the opposite. A quick visit to Google Maps and its live scrollable map tiles or NetVibes and its drag-and-drop reorganization of your personal data both show how potent and compelling Ajax techniques really are.
I originally covered the current state of Ajax back in August in a widely linked article. It still provides a good summary of the history, benefits, and pitfalls of Ajax but it's amazing what has happened since then. It's also interesting to see what issue haven't been resolved. Though Ajax isn't a technology, it's strictly constrained by the technologies that it uses to describe how to weave visually arresting, highly intereactive, web service-based applications that can be loaded into any browser with a single URL, all without installing any software. But some challenges continue to remain but are decreasing in concern.
The term and world-wide attention behind Ajax is not even a year old, but you can find a wide range of poweful tools either with newly added support for Ajax or created just to support the Ajax way of life. In addition, many of the constaints and problems with Ajax have been resolved or greatly reduced. But keeping track of all these developments is very difficult, so I've compiled a summary here of the major advances in Ajax so far this year.
I hope you enjoy. And as always, please add your own at the bottom for all to benefit...
Improved Ajax Techniques
- 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.
- 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.
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.
And don't forget to see what can be done with Ajax! Check out these great new Ajax-enabled applications here.
posted Friday, 30 December 2005
]]>