Web Services: Difference between revisions
No edit summary |
|||
Line 13: | Line 13: | ||
default. If you want to develop a full featured management system then it is usually a bad idea to |
default. If you want to develop a full featured management system then it is usually a bad idea to |
||
start with a small PHP script because everbody will extend the script until the complete system |
start with a small PHP script because everbody will extend the script until the complete system |
||
breaks. |
|||
⚫ | |||
⚫ | |||
# [[Web_Services_Language|Language]] |
# [[Web_Services_Language|Language]] |
Revision as of 07:19, 9 March 2007
Web Services
This page does not contain any theoretical discussions of web services. It is more a practical guide to develop such services. The whole stuff is not complete yet. So let's start.
You should really careful think about design before you should start coding a web service. The first line of java code in our actual project was written about six months after we started thinking about the design. To be fair - we developed a prototype in Perl to demonstrate some basic features of the architecture. The problem is, if you start the coding process which is described here then you must have a complete idea about your design and requirements. Many decisions depend on these facts. A web service does not mean Java or SOAP or anything else by default. If you want to develop a full featured management system then it is usually a bad idea to start with a small PHP script because everbody will extend the script until the complete system breaks.
So first design and second start coding.
- Language
- IDE
- Application Server
- Framework
- WSDL
- WS Security
- Deployment