|
Updated: 9/1/2002; 7:00:04 PM.
 |
Wednesday, April 10, 2002 |
Scott Seely Evolving an Interface [Snell's Blog]. Hmmm. If those are the rules that one should follow, then I have a hard time understanding why ASP.NET ignores values it doesn't expect and provides defaults for parameters it does expect. One must also consider what happens when people other than the originator want to extend the interfaces. My thoughts on the subject are captured in Coping with Change.
4:02:43 PM 
|
|
Matt Griffith: MapPoint .NET uses the HTTP Digest ... What does this mean for non-Microsoft SOAP clients? Which platforms will be able to call MapPoint.NET easily? Which will have trouble? Excellent question! I've posted Matt's questions to SOAPBuilders. Thanks, Matt!
12:22:06 PM
|
|
HP SOAP 2.0: SOAP server and XML document processing pipeline controlled by the Apache Cocoon2 framework
9:13:25 AM
|
|
Tim O'Reilly: Inventing the Future. What's hot?
- Wireless
- Next generation search engines
- Weblogs
- Instant messaging
- File sharing
- Grid computing
- Web spidering
8:39:18 AM
|
|
Jon: SOAP security and external underwear. Agreed. Never saw Bananas, but that's an excellent analogy. SOAPaction should go.
7:37:50 AM
|
|
|
