Convincing web service migration
-
I am currently involved in a project that is a distrubeted network for sharing medical teaching cases between hospitals. It operates kind of like a specialized kazaa. The current system is in beta. It uses java servlets to send custom HTML messages between the querying program and the stroage server. I thought that it could be better implemented using a web service. Firstly the implementation would be more elegant from a programming stand point. Second, web services are a good technology base for future work. They are full featured and the functionality is constantly being expanded. The engineer in charge of the project has no knowledge of SOAP at all and he has been resistant to my ideas. He does report to a committee that overseas the project. What would be the best way to convice people that the project should use web services? I need more than the fact that it is cooler and technologically superior. Thanks. Steve Not all who wander are lost...
-
I am currently involved in a project that is a distrubeted network for sharing medical teaching cases between hospitals. It operates kind of like a specialized kazaa. The current system is in beta. It uses java servlets to send custom HTML messages between the querying program and the stroage server. I thought that it could be better implemented using a web service. Firstly the implementation would be more elegant from a programming stand point. Second, web services are a good technology base for future work. They are full featured and the functionality is constantly being expanded. The engineer in charge of the project has no knowledge of SOAP at all and he has been resistant to my ideas. He does report to a committee that overseas the project. What would be the best way to convice people that the project should use web services? I need more than the fact that it is cooler and technologically superior. Thanks. Steve Not all who wander are lost...
Steve Severance wrote: What would be the best way to convice people that the project should use web services? I need more than the fact that it is cooler and technologically superior. Thanks. The cool thing about web services is that they don't need to be the only API you provide to your system. You can also provide alternative solutions, like traditional (simpler) socket APIs, and so on. If you're stuck with pure C on an old UNIX machines, SOAP messages can be hard to hand-code. Therefore, my advice is: provide alternative implementations to ease access from older technologies, and make those alternative APIs consistent with the Web Service. When the time comes, almost everyone will migrate to the most efficient technology.
// Quantum sort algorithm implementation
while (!sorted)
; -
I am currently involved in a project that is a distrubeted network for sharing medical teaching cases between hospitals. It operates kind of like a specialized kazaa. The current system is in beta. It uses java servlets to send custom HTML messages between the querying program and the stroage server. I thought that it could be better implemented using a web service. Firstly the implementation would be more elegant from a programming stand point. Second, web services are a good technology base for future work. They are full featured and the functionality is constantly being expanded. The engineer in charge of the project has no knowledge of SOAP at all and he has been resistant to my ideas. He does report to a committee that overseas the project. What would be the best way to convice people that the project should use web services? I need more than the fact that it is cooler and technologically superior. Thanks. Steve Not all who wander are lost...
web services aren't just only to SOAP. You can transport via HTTP and FTP The good thing about web services is any language can tie into them using DISCO and hook to a wsdl. But there a huge security risk, hackers can easily get past firewalls since firewalls dont guard agains web services. tpyically though becuase I heard some are sifting for unusual data. But send jsp http requests to update data seems kind of old-world since web services are easier and less code means easier maintainable. Which in your employers eyes means more product for less money. If you want it to fly the keyword is "real world experiences saving MONEY" do some research and make a 3 page report. but youll create an enemny. be forwarned. I'm not an expert yet, but I play one at work. Yeah and here too.