A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Waterfall_Cache has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 47

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 194

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Memcache_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 275

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Filesystem_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 440

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; APC_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 628

Grok It Page 4

Grok It Page 4

By Nelson King (Send Email)
Posted Mar 28, 2002


Because Web services will probably have varied effect on different industries, it is helpful to read or hear case stories from peers. This will enable you to develop a sense for how Web services are applied and perhaps learn some of the caveats and gotchas. In the end though, you must acquire an intuitive feel for what Web services are and how they can be applied. That is usually the result of trying it for yourself.

A year or so ago it might have been advisable to use some of the kits that were just appearing (e.g., the Microsoft SOAP Kit), but we think that's no longer appropriate. Full-scale Web services tools have been released in many different forms, and organizations should experiment with tools that reflect its normal choice of languages and development environments. For example, an IBM shop ought to be working with IBM WebSphere Studio and the Web Services Extensions. Likewise, Microsoft shops should be working with the relevant portions of Visual Studio .Net.

Keep in mind that it might be difficult for one person to master all of the necessary elements of Web services -- SOAP, WSDL, and especially XML can require ascending a major learning curve.



Comment and Contribute

Your name/nickname

Your email

(Maximum characters: 1200). You have characters left.


 

 


Thanks for your registration, follow us on our social networks to keep up-to-date