鍦ㄧ綉涓婃壘浜嗗緢涔呮墠鎵懼埌developerWorks涓婄殑涓涓В鍐蟲柟妗堬細
鍦ㄥ懡浠ゆ彁紺虹閲屽垏鎹㈠埌鐩綍“C:\Program Files\IBM\SDP70\jdk\jre\bin”錛岃繍琛?#8220;java.exe -Xshareclasses:destroyAll”
榪欐牱灝辮兘姝ｅ父鍚姩RAD浜嗭紒
鍘熷洜鎻忚堪濡備笅錛?/p>
錛堟憳褰曡嚜http://www-1.ibm.com/support/docview.wss?uid=swg21281393錛屽茍閫氳繃Google Translate杞瘧錛岃瘧鏂囧凡浣滀慨鏀癸級
×××××××××××××××××××××××××××××××××××××
闂錛堟憳瑕侊級
姝よ鏄庤В閲婂浣曡В鍐抽敊璇?#8220;JVM鐨勭粓姝€傞鍑轟唬鐮? 1”銆?br />
璧峰洜
RAD鑷甫鐨処BM JVM浣跨敤浜嗕竴涓珮閫熺紦瀛樺弬鏁版潵鎻愰珮鎬ц兘銆傝屽洜涓篔VM鐨勫穿婧冿紝姣斿钃濆睆錛屾垨鏂數錛岄兘鍙兘閫犳垚Java楂橀熺紦瀛樿鎹熷潖銆?鑰孞VM浼氭嫆緇濊繛鎺ュ埌涓涓崯鍧忕殑楂橀熺紦瀛樸?/p>
瑙ｅ喅闂
瑕佽В鍐寵繖涓棶棰橈紝浣跨敤“-Xshareclasses:destroyAll”鐨凧ava閫夐」灝嗛攢姣佹墍鏈夌殑鍏變韓綰х紦瀛樸傝繖鏄竴縐嶅疄鐢ㄥ伐鍏烽夐」錛屾墍浠ヤ笉浼氬惎鍔↗VM 銆傚鏋滄偍鎯寵榪欎箞鍋氾紝鍙浠庡懡浠ゆ彁紺虹浣跨敤鍙傛暟“-Xshareclasses:destroyAll”鏉ヨ繍琛孯AD浣跨敤鐨刯ava銆?/p>
××××××××××××××××××××××××××××××××××××××
]]>
浠庝竴澶у爢涔辯爜涓壘鍑哄彲浠ョ悊瑙ｇ殑淇℃伅錛堝瓧姣嶏級
Java瑙ｅ喅鏂規錛?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)
);
}
}
闄凱ython鍜孲hell錛?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瑙ｅ喅鏂規錛?
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鍜孲hell瑙ｅ喅鏂規錛?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]
]]>
]]>
鏂規硶錛氬惈涓澶у彛姘達紝灝忓彛鍒嗗嬈″悶涓嬶紝鐩磋嚦涓嶆墦鍡濄?錛堜竴鑸袱澶у彛姘撮噺灝卞彲浠ユ悶瀹氾級
PS: 浠ｇ爜瀹炵幇錛?br>
while(鎵撳棟)
{
for(int index=0; index<2; index++)
{
鍚竴澶у彛姘達紱
while錛堝彛涓繕鏈夋按錛?br> {
鍚炰竴灝忓彛錛?br> no sleep錛?br> }
no sleep錛?br> }
sleep 5縐掞紱
}
{
for(int index=0; index<2; index++)
{
鍚竴澶у彛姘達紱
while錛堝彛涓繕鏈夋按錛?br> {
鍚炰竴灝忓彛錛?br> no sleep錛?br> }
no sleep錛?br> }
sleep 5縐掞紱
}
]]>
1銆乯sp:usebean鏍囩涓紝 鑻ュ紩鐢ㄧ殑bean涓嶅瓨鍦紝浼氳嚜鍔ㄨ皟鐢ㄩ粯璁ゆ瀯閫犲櫒鐢熸垚涓涓猨avabean瀹炰緥錛屾墍浠ヤ笉瑕佸湪servlet閲屽啀鐢╯ession.getAttribute鏉ュ垽鏂璪ean鏄惁涓虹┖錛堝洜涓鴻偗瀹氫笉涓虹┖錛夛紝搴旇鍒ゆ柇閲岄潰鐨勫瓧孌墊槸鍚︿負null鎴栦負鍒濆鍖栫姸鎬併?/p>
2銆乯sp:usebean 鐨刢lass灞炴у簲璇ユ槸綾葷殑鍏ㄥ悕錛堝寘鎷寘鍚嶏級銆傚湪鍓嶉潰<%@ import>涓璱mport鐨勫寘錛屽湪tag閲屼笉璧蜂綔鐢紝鍙jsp閲岄潰鐨刯ava浠ｇ爜鏈夌敤錛屾墍浠ag閲岃浣跨敤綾葷殑鍏ㄥ悕
3銆乸ost鏃跺鏋滆〃鍗曢噷鏈変腑鏂囷紝浼氬嚭鐜頒腑鏂囦貢鐮侊紝鍦╯ervlet閲岃皟鐢╮equest.getParameter涔嬪墠鎵цrequest.setCharacterEncoding("gb2312");灝卞彲浠ユ紜瘑鍒拰鏄劇ず涓枃浜嗭紱
濡傛灉鏄痷rl涓敤涓枃鍙傛暟錛屽someaction.jsp?q=涓枃闂錛屽垯瑕佸姞涓涓猣ilter鏉etEncoding錛屽洜涓簆ost鍜実et浼犻佸弬鏁扮殑澶勭悊鏂瑰紡涓嶄竴鏍楓倁rl涓寘鍚腑鏂囧弬鏁扮殑璁劇疆鍙傝冿細http://www.itet.cn/0512456328001529/JSP/0691214511318687.html
]]>
]]>
String聽sql聽
=
聽
"
select聽s.name聽from聽student聽s聽where聽s.id='
"
聽
+
聽sId聽
+
聽
"
'
"錛?/span>
鍚庢潵鎴戝紑濮嬩嬌鐢?strong>PreparedStatement錛屽湪SQL閲屼嬌鐢ㄢ滐紵鈥濇爣璁板弬鏁幫紝鐒跺悗鐢╯etXXX鏂規硶緇欏弬鏁拌祴鍊箋傚綋鏃跺彧鐭ラ亾榪欐牱鐢ㄦ槸鍥犱負鏈?strong>setDate錛宻etTimeStamp榪欎簺鐢ㄢ?鈥濊繛鎺ヤ笉鑳界洿鎺ュ祵鍏ョ殑鍊箋?br />
鎰熻PreparedStatement鍦?strong>鎬ц兘鏂歸潰搴旇涔熻兘蹇偣錛屽彲鑳紻BMS浼氶噸鐢紝浣嗕笉鏄庡簳灞傚師鐞嗐?br />
榪欐銆婃暟鎹簱瀹炵幇銆嬭紼嬬粓浜庤鎴戝紕鎳備簡錛?strong>姣忎釜SQL璇彞閮借閫氳繃 璇硶鍒嗘瀽 -> 鐢熸垚閫昏緫鏌ヨ璁″垝 -> 閫昏緫浼樺寲 -> 鐗╃悊浼樺寲 絳夋楠ょ敓鎴愬叿浣撶殑鎵ц璁″垝錛岀敤PreparedStatement灝卞彲浠ョ敓鎴愪竴涓墽琛岃鍒掞紝浠ュ悗鍙槸鍙傛暟鏀瑰彉錛堢浉褰撲簬鎵ц璁″垝鐨?strong>鎵ц鐜鏀瑰彉錛夛紝鍓嶉潰鐨勫洓涓楠や篃浼?strong>鐪佺暐錛屼粠鑰屾彁楂樹簡鏁堢巼銆?br />
濡傛灉涓涓猄QL璇彞瑕佽鍙嶅澶氭鎵ц錛屾垨澶氱敤鎴峰悓鏃舵搷浣滐紝鍒欏簲閫夌敤PreparedStatement錛?/p>
]]>
]]>
濡備笅浠ｇ爜鎵紺猴細
//灝嗘帴鏀跺埌鐨勬暟鎹瓨鍒板瓧鑺傛暟緇刟rrayint聽firstChar聽=聽inputStream.read();int聽length聽=聽inputStream.available();byte[]聽array聽=聽new聽byte[length+1];array[0]聽=聽(byte)firstChar;inputStream.read(array,1,length);]]>
鏈鍚庝綔鑰呬互Struts涓轟緥錛屼粙緇嶄簡鍑犵閫夋嫨Ajax鐨勫満鏅細
1 鐜版湁鐨凷truts搴旂敤紼嬪簭瑕佷嬌鐢ˋjax錛岃浣跨敤AjaxAnywhere
2 寤虹珛鏂扮殑搴旂敤紼嬪簭鍑嗗浣跨敤Ajax錛屽弬鑰傾ppfuse錛屽畠闆嗘垚浜咲WR鐨凙jax
3 涓湡鐩爣錛?浣跨敤涓縐嶆敮鎸丄jax鐨凧SF鐨勫疄鐜幫紝MyFaces鎴栬匰truts Shale
鍘熸枃鍦板潃錛?A >http://blog.csdn.net/danny_xcz/archive/2006/03/03/614302.aspx
]]>
姝ラ錛?BR>
1銆佸湪搴旂敤紼嬪簭鏂囦歡鏍圭洰褰曚笅鏂板緩涓涓狹ETA-INF鐩綍錛屽湪璇ョ洰褰曚笅鏂板緩MANIFEST.MF鏂囦歡錛?
鏂囦歡鍐呭涓猴細
1 Main-Class: 鍖呭悕.涓葷被鍚?nbsp;
2
3
2
3
2銆佸皢搴旂敤紼嬪簭鏍圭洰褰曚笅鎵鏈夋枃浠剁敤winrar鎴杦inzip鎵撳寘錛屾牸寮忎負zip錛?
3銆佸皢zip鏂囦歡鎵╁睍鍚嶆敼涓簀ar 錛?BR>
4銆佸弻鍑籮ar鏂囦歡鍗沖彲榪愯銆?
甯屾湜鑳藉澶у鏈夌偣甯姪銆?img src ="http://www.tkk7.com/Andyluo/aggbug/31057.html" width = "1" height = "1" />
]]>
]]>
緇勪歡鍥?/a>
綾誨浘
浜嗚В緇撴瀯浜嗗氨寮濮嬬湅鍚э紝go
]]>
Class.forName("weblech.util.Log4j");
鍏朵粬濡傛敞鍐屾暟鎹簮銆佺晫闈㈡湰鍦板寲銆傘傘?BR>
Eclipse鐪嬩唬鐮佹槸鏈鐖界殑錛?BR>鏌ョ湅綾葷殑寮曠敤銆佷唬鐮佸鑸?img src ="http://www.tkk7.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鎴栬単et鑾峰緱form琛ㄥ崟鐨勬暟鎹紝閭ｄ箞鎴戜滑濡備綍瀹炵幇涓嶅埛鏂扮殑鎻愪氦鐩存帴鑾峰緱欏甸潰涓婄殑鏁版嵁鍛紵榪欏氨瑕佸熷姪xmlhttp鍗忚浜嗐倄mlhttp鏄痻mldom鎶鏈殑涓閮ㄥ垎銆?BR>銆銆
銆銆涓嬮潰鐨勪唬鐮佸氨鏄竴涓緢綆鍗曠殑渚嬪瓙錛屾垜浠埄鐢▁mlhttp鎶鏈疄鐜扮畝鍗曠殑鐢ㄦ埛鐧婚檰銆?BR>銆銆
銆銆寮濮?/B>
銆銆
銆銆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);銆//鍙鐞嗗悗鍙拌繑鍥炵殑緇撴灉
銆銆}
銆銆
銆銆濮撳悕錛?lt;input type="text" id="name" /><br>
銆銆瀵嗙爜錛?lt;input type="text" id="pwd" /><br>
銆銆<input type="button" value="鐧誨綍" onclick="toServer()">
銆銆
銆銆2.鍚庡彴鐨勭櫥褰曞鐞嗛〉闈?BR>銆銆do_login.jsp
銆銆
銆銆<%
銆銆//璇誨彇XMLHTTP嫻?BR>銆銆java.io.BufferedReader br =銆request.getReader();
銆銆String str = "";
銆銆while (str != null) {
銆銆str = br.readLine();
銆銆process (str); //鍙氳繃浠諱綍璇█瀹炵幇瑙ｆ瀽XML錛岃繘琛屼笟鍔″鐞?BR>銆銆}
銆銆
銆銆//榪斿洖淇℃伅
銆銆javax.servlet.ServletOutputStream sos = response.getOutputStream();
銆銆sos.print("login success" );
銆銆sos.close();
銆銆%>
銆銆涓庝紶緇熺殑鈥滄彁浜わ紞鍥炲彂錛嶉噸緇樷濆紡鐨剋eb緋葷粺鍩烘湰榪愯緇撴瀯涓嶅悓錛屾垜浠彲浠ラ氳繃閫氳繃XMLHTTP瀹炵幇鏃犲埛鏂扮殑瀹㈡埛绔洿鎺ヤ笌鏈嶅姟鍣ㄤ氦浜掞紝鏋佸ぇ鐨勬彁楂樼敤鎴風殑鎰熷彈搴︺?BR>銆銆
銆銆鏌ヨ冭祫鏂?/B>
銆銆
銆銆XMLHTTP鏂規硶錛?BR>銆銆
銆銆Open bstrMethod, bstrUrl, varAsync, bstrUser, bstrPassword
銆銆bstrMethod錛氭暟鎹紶閫佹柟寮忥紝鍗矴ET鎴朠OST銆?BR>銆銆bstrUrl錛氭湇鍔＄綉欏電殑URL銆?BR>銆銆varAsync錛氭槸鍚﹀悓姝ユ墽琛屻傜己鐪佷負True錛屽嵆鍚屾鎵ц錛屼絾鍙兘鍦―OM涓疄鏂藉悓姝ユ墽琛屻?BR>銆銆搴旂敤涓竴鑸皢鍏剁疆涓篎alse錛屽嵆寮傛鎵ц銆?BR>銆銆bstrUser錛氱敤鎴峰悕錛屽彲鐪佺暐銆?BR>銆銆bstrPassword錛氱敤鎴峰彛浠わ紝鍙渷鐣ャ?BR>銆銆
銆銆Send varBody
銆銆varBody錛氭寚浠ら泦銆傚彲浠ユ槸XML鏍煎紡鏁版嵁錛屼篃鍙互鏄瓧絎︿覆錛屾祦錛屾垨鑰呬竴涓棤絎﹀彿鏁存暟鏁扮粍銆備篃鍙互鐪佺暐錛岃鎸囦護閫氳繃Open鏂規硶鐨刄RL鍙傛暟浠ｅ叆銆?BR>銆銆
銆銆setRequestHeader bstrHeader, bstrValue
銆銆bstrHeader錛欻TTP 澶?header)
銆銆bstrValue錛欻TTP 澶?header)鐨勫?BR>銆銆濡傛灉Open鏂規硶瀹氫箟涓篜OST錛屽彲浠ュ畾涔夎〃鍗曟柟寮忎笂浼狅細
銆銆xmlhttp.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
銆銆
銆銆XMLHTTP灞炴э細
銆銆
銆銆onreadystatechange錛氬湪鍚屾鎵ц鏂瑰紡涓嬭幏寰楄繑鍥炵粨鏋滅殑浜嬩歡鍙ユ焺銆傚彧鑳藉湪DOM涓皟鐢ㄣ?BR>銆銆responseBody錛氱粨鏋滆繑鍥炰負鏃犵鍙鋒暣鏁版暟緇勩?BR>銆銆responseStream錛氱粨鏋滆繑鍥炰負IStream嫻併?BR>銆銆responseText 錛氱粨鏋滆繑鍥炰負瀛楃涓層?BR>銆銆responseXML錛氱粨鏋滆繑鍥炰負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
]]>