Recent three-story practice I have produced "Thians" ideas for DCOM, SOAP, etc. The integration of DCOM and Windows permissions makes deployment still not very perfect: Borland's Midas's implementation is more difficult, it wants to register on the client :); Server wants to run once in the client to register the interface People are not cool; they are all in the field, and there is actually some normal use programs. I really don't understand how to deal with it.
Summary: Multi-layer development of DCOM is either a client server in the same field (and the user logs in to the domain), or the user currently logged in is the same on the server and the password is the same.
SOAP I simply understand TCP communication using XML delivery information (common for http / https), wrote some testing WAD, CGI, the same machine test is OK, and the data can be passed with SOAPDATAMOUDLE and interface. The high line test is prompted: "XML must have a top element"? ? The reason is not yet found.
Summary: It seems that the same machine is not related to the same machine. It is still an error, not ignorant, is there any problem? Have the opportunity to check which floor has a problem.
The new idea, since SOAP has been embedded in the XML page of HTTP, how do you need multiple layers? No need for the time being (the current three layers is enough). Do you need a business? not needed for now. Do you need high security? not needed for now. Do you need a cross-platform? not needed for now. Do you need to interact with other languages? not needed for now. Rely, it is a tossible, you have to just a thin client than B / S "fat", reaching the purpose of deploying convenient upgrade, realizing the three-story and only those orthodox methods, so I plan to do it as follows, use CGI or ISAPI to do binary or XML data (can also consider compression), the client is not big, DCOM, Soket ..., Web ..., Soap these things directly receive HTTP sent Binary data or XML, the same achievement, roughly speculation should not encounter the above problems. Efficiency should not be too bad, firewall, etc., you can't nail, why, I am waiting to practice.
Oh, this idea may be none by some professional, but it can solve my problem :) Welcome criticism finger ^ _ ^
