Max's Blog

目前在Windows平台下代理服务器软件产品主要有：Microsoft Proxy，Microsoft ISA，Netscape Proxy、WinProxy、WinGate Pro、winRoute、SyGate以及CCProxy等等。

  由于目前HTTP应用最广泛，因为http代理的实现也是最重要的。http代理又有两种认证方式： Proxy Basic认证和Proxy NTLM认证。

  Proxy Basic认证一般用于 不太重要的场合，因为Basic认证时直接把用户名密码变一下形就从网络上传过去了，随便sniffer一下就能把这个 数据截获从而得到 密码。

 Proxy NTLM认证用于正式场合，它的认证方式与Windows远程登录的认证方式是一样的，需要三次握手传递信息，不在认证的过程中传递密码，而且，每次认证传递的信息都不一样。

 Proxy NTLM认证 涉及到 复杂的密码算法及公钥机制，所以很多软件都没有实现通过这种方式使用代理，然而不少的公司内网都是用NTLM认证的代理限制员工上网，下面介绍了如何把NTLM的代理转变为本机普通HTTP代理：

需要安装PYTHON，然后下载 NTLM authorization Proxy Server

这个是Python写的，所以必须先安装Python运行环境。下载了NTLM APS以后，直接解压，不要管那个bat文件，直接双击main.py即可运行。不过在运行之前必须先配置一下：

打开server.cfg，修改以下参数：
PARENT_PROXY:代理的IP
PARENT_PROXY_PORT:代理的端口
NT_DOMAIN:你的域
USER:用户名
PASSWORD:密码

实在是很简单吧。这样就搞定了。运行main.py以后就在本地生成了一个普通HTTP代理，端口是5865。

eMule个人数据备份：

换eMule时可以使用网友绿色西瓜的批处理工具“04XEmuleBack”对Config文件夹进行备份，以便于转移。

NeoMule4.25的clients.met[信用文件，记载他人信用]已使用官方版本的格式，但是格式刚换新所以可能会有点问题：
NeoMule互copy时必须clients.met、clients2.met都copy才行（已写入上述批处理工具），否则可能会出错
NeoMule拷贝到Xtreme或官方eMule时，可以将NeoMule的clients.met先拷贝到MorphXT，打开MorphXT再关掉以转换其格式，再把MorphXT的这个clients.met拷贝到Xtreme或官方eMule

另注：其他版本copy到NeoMule均正常

备份文件列表：

cryptkey.dat 安全认证
preferences.dat userhash
clients.met 信用文件
clients2.met NeoMule信用文件
emfriends.met 好友列表
known.met 已知文件信息[包括hash，上传数等]
known2_64.met AICH hash相关，存放文件的hash值
preferences.ini EM的配置文件，同时存放旧版的统计数据[0.43以前]
Category.ini 下载分类
fileinfo.ini 文件注释
statistics.ini 新版的统计数据[0.43及以后的版本]
shareddir.dat 共享的目录
staticservers.dat 静态服务器列表
server.met 服务器列表
preferencesKad.dat Kad网络上的userhash

hibernate能支持这种方式，一对零或一，但是不能做到lazy，今天搞cdr搞了一天，锁死在这个问题上面了，暂时无解

 cdr的表已经400多w数据了，而且字段有nn个，这次新加的属性也不是每条都用到，所以是一个one to zero or one的关系，但是hibernate怎么搞都不能做到lazy，这样如果搜索很多cdr的时候就造成join表或者select过多。。。很郁闷。到官方论坛找了一下，貌似这个问题暂时无解。。。摘录一点评论：

from http://forum.hibernate.org/viewtopic.php?t=949458

1、

The problem is that sometimes we really need a lazy “one-to-zero-or-one” relationship. If we would change to a lazy one-to-one we would have to use the constrained attribute in ‘one-to-one’ element which forces a not null attribute. But sometimes a person doesn’t have a note.The use of “many-to-one” mapping that we did fits perfectly to our needs. It gets a proxy when we don’t use eager fetching. It gets the right note when we use eager fetching, but it gets a proxy when there is no note associated to the person. So it works almost perfectly, except that when we force eager fetching in null notes, Hibernate hydrates person objects with a proxy and not with a null reference.I know that I could add a FK in note table and solve my problem, but why should I do that if I can use the same person PK? If Hibernate would return null when there is no note it would be just right. I just would like that the following mapping should work as stated above. I think that when we get a proxy when an eager fetching is used is an inconsistent result. In our case, we are using a workaround to detect and fix this situation, but we wanted to report it as a way to help other people who may face the same problem and maybe to help Hibernate become even better.Many-to-one mapping:

Our problem is not so rare. We found other people in this forum facing the same lazy “one-to-zero-or-one” problem, but the solutions were “non-lazy one-to-one mapping”, “lazy not-null one-to-one mapping using constrained=”true”” or “many-to-one mapping using a foreign key (FK)”. We are suggesting one more solution to the problem: “many-to-one mapping using the same primary key (PK)”. I hope that can help someone else.
 

2、

Hibernate cannot replace a proxy with a null, this is not possible in Java wo bytecode enhancement.
So wo does hibernate know whether it needs to create a proxy or set null? The only solution is to load the second row. Check the wiki comunity area, there is a page dedicated to the non one-to-one lazyness

3、 The use of not-found=”ignore” results in a non-lazy property. So lazy “one-to-zero-or-one” in Hibernate is not possible yet. We can use non-lazy “one-to-zero-or-one” or a lazy one-to-one association. 4、hibernate teamHi guys,Just a small comment – there is *no* problem in using polymorpishm with respect to associations in hibernate. The issue you have is about representing NULL, something that is more related to the kind of datamodelling people tend to do and not OO. The users I see having problem with polymorphic associations are mostly those who want to downcast their objects which again is something that is arguable OO.And note, that just because there *can* be a association defined between two objects, doesnt mean it *has* to be physically represented in your object model.In any case, all is possible now with H3.1, so go buy your bigger machines 😉

补充：

下班前终于想到一个临时方法搞定。。。贴到hibernate。。。用one to many 来实现，会好看一点，呵呵

i think i have this problem today , i don’t know whether hibernate team has resolved this problem or not after two years…(the last post is 2005…)and i think a temp solution:
use one-to-many instead , i think one to many includes one to zero or one or many….
and for one to zero or one , wirte a bean method to handle the Set/List and get the real one value….<set name=”notes” table=”Note” inverse=”true” lazy=”true”>
<key column=”owner”></key>
<one-to-many class=”Note”/>
</set>