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

The Web Services Value Chain Page 4

The Web Services Value Chain Page 4

By ServerWatch Staff (Send Email)
Posted Aug 30, 2001


By Jean-Christophe Cimetiere of TechMetrix Research

Several solutions already dedicated to Web services development include CapeClear's CapeConnect Web Services Platform, Lucin's SAL Server, SQLData System's SOAP Server, The Mind Electric's Glue Platform, and Bowstreet's Business Web Factory.

As we have noted previously, application server vendors are doing their homework, but at this time most of them are "patching" their products with SOAP libraries and basic listeners. This leaves some room for new players with cutting-edge solutions.

Tbere are, however, benefits of going with either option.

Advantages of "Classical" App Servers Advantages of "New" Web Services Servers
Use/re-use of existing components and business objects Productivity of the tools for Web services enablement
Performance and reliability (e.g., load balancing and failover) Compliance with standards



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