Breakfast tomorrow
Summary of decision tree for Addr/Desc groups
Trusting callback endpoints
Agenda: 2005-02-23 Async TF telcon
DRAFT minutes from 2005-02-16 telcon
Additional use case: 7 "Reversed HTTP binding for SOAP".
- Re: Additional use case: 7 "Reversed HTTP binding for SOAP".
- RE: Additional use case: 7 "Reversed HTTP binding for SOAP".
Point of view in operation descriptions.
Usecase 4: Asynch req-res -- polling style
Use case 5
Use case 3
Use case 1 - one way
Use Case #2, sync req-resp over the same connection
Agenda: 2005-02-16 Async TF telcon
REMINDER : Action Items re: Use Cases
Use case 6
Minutes of the 2005-02-09 teleconference
Use case similar to #6, but sync/async decision is made at deployment time, not run-time
Async use cases
Agenda: 2005-02-08 Async TF telcon
Scoping multi-transport / async bindings for WSDL
- RE: Scoping multi-transport / async bindings for WSDL
- RE: Scoping multi-transport / async bindings for WSDL
- Re: Scoping multi-transport / async bindings for WSDL
- Re: Scoping multi-transport / async bindings for WSDL
RE: Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
RE: Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
- Re: Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
- RE: Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
- RE: Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
- RE: Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
RE: Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
Initial thoughts on WSDL2.0 LC101 - do we need message level binding properties?
Mailing list failures: explanation and possible fix
HTTP based async request-response
- RE: HTTP based async request-response
- RE: HTTP based async request-response
- Re: HTTP based async request-response
- Re: HTTP based async request-response
- RE: HTTP based async request-response
- RE: HTTP based async request-response
- RE: HTTP based async request-response