Kim-'s-Blog.Object-Everything.I'm POJO.

http://hashkiller.com/password/
Password:sa
 
Common Hashes
 
md5： c12e01f2a13ff5587e1e9e4aedb8242d
md4： f9145896fbc42dac61e7fdeeef2f9938
md2： cdfed67a6621b8b97c5e58c5fd6d6b86
sha1： 3608a6d1a05aba23ea390e5f3b48203dbb7241f7
sha256： 4cf6829aa93728e8f3c97df913fb1bfa95fe5810e2933a05943f8312a98d9cf2
sha384： 4b7d79fd9e55caac33d50b5d5337899adc8be5e7a1c55446f514104a427cf9859c47284a663af817bd3b2478a578ea4e
sha512 30a76625d5fc75e3ab6793b19819935e65e43cf3745832061cb432a5de7fdc17d66ede
77973d5aed065bc7e3e0536ebcc5129506955574e230b92b71bd2cb1c7
LM： 551ad95ba854afdcaad3b435b51404ee
NT： 9cb285c0622b8e5e8181a2b3d1654c17
base_64： c2E=
rot_13： fn

http://hashkiller.com/   
還可以
MD5反編譯

在CXF Client 調(diào)用是總是出現(xiàn)這個(gè)錯(cuò)誤。
我用的是JDK6.0
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
變成了
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
加一句
System.setProperty("javax.xml.parsers.DocumentBuilderFactory", "com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl");
不會(huì)出現(xiàn)這個(gè)錯(cuò)誤
但會(huì)
java.lang.NoSuchMethodError: javax.xml.parsers.DocumentBuilderFactory.getSchema()Ljavax/xml/validation/Schema;
連方法都變了 暈哦

在往Spring2.0項(xiàng)目中添加XFire時(shí)（Myeclipse）出現(xiàn)如下錯(cuò)誤
Document root element "beans", must match DOCTYPE root "null".
原因：XFire Core lib 中有Spring1.2.6 與Spring 2 沖突！

可以這樣寫：
execution(* com.foo..*.*(..)) and !execution(* com.foo.bar..*.*(..)).

every method in com.foo but not in com.foo.bar.

封裝有它的好處，使用封裝可以掩蓋細(xì)節(jié)，（如Spring.JSF.Hibernate.Spring還會(huì)留好多回調(diào)接口），對于封裝我的看法是：要做到 想進(jìn)就進(jìn)，想出就出，隨心所欲。提升自己的境界。（最近在做一個(gè)框架有感）

要回武漢了，告別深圳中...
最近很忙的，以后有時(shí)間一定常來看看

When a method is idempotent, in short, you are guaranteeing that regardless of when or how often it's used, no "side effects" will occur.

對每一個(gè)相同的query string
不管你執(zhí)行多少次
所得到的結(jié)果要一樣

doPost()

This method does not need to be either safe or idempotent. Operations requested through POST can have side effects for which the user can be held accountable, for example, updating stored data or buying items online.

     摘要: Dos命令有必要再復(fù)習(xí)下...
Ant 有可能用到。
------------------------------------------------------------------------------
第1、最常用的命令
　　cd　　　　　改變當(dāng)前目錄　　　　　　　sys 　　制作DOS系統(tǒng)盤

　　copy　　　　拷貝文件　　　　　　　　　del 　　刪除文件

　　deltree　 　刪除目錄樹　　　　　　　　dir 　　列文件名

　　diskcopy　　制磁盤　　　　　　　　　　edit　　文本編輯

　　format 　　 格式化磁盤　　　　　　　　md　　　建立子目錄

　　mem 　　　　查看內(nèi)存狀況　　　　　　　type　　顯示文件內(nèi)容

　　rd　　　　　刪除目錄　　　　　　　　　ren 　　改變文件名 ..........
  閱讀全文

Distributed Computing: an abstract concept. Very general.

Cluster: tightly-coupled distributed computing. A Cluster is usually inside the same room, using same computers, same OSs, connected using dedicated clustering software.

Grid: loosely-coupled distributed computing. A Grid is usally dispersed anywhere far-away from each other, and you do not know what computers, what OS on each node, you only know they communicate via HTTP(s)/XML in a black-box style. More flexible.

Parallel Computing: very tightly-coupled distributed computing, like a few CPUs inside a PC. Parallelism was a dream in 1980-1990 but that concept failed, because many things cannot be split into parallel tasks. The overhead to write parallel algorithm is tramendous. People no longer use this term much these years.

P2P: an extremely loosely-coupled distributed computing. Since the name was ruined by Napster, people try to avoid using this term in their serious projects.

In particular, for Cluster vs. Grid, I have some further comparison:

Cluster: PCs inside a same locked room; Grid: distributed, not in same room.

Cluster: ususally same OS, same machines; Grid: very different unknown platforms;

Cluster: tightly-coupled system; Grid: loosely-coupled system.

Cluster: bound together by TCP/IP on LAN; Grid: connected by HTTP/XML on WAN.

Cluster: like teamwork; Grid: like collaboration

Hibernate
Ibatis

出現(xiàn)N+1? Select時(shí)，可以通過外連接，或?qū)慞rocedure解決。