[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
Re: [xml-dev] Transformative Programming: Flow-based, functional, and more
- From: Peter Hunsberger <peter.hunsberger@gmail.com>
- To: "Simon St.Laurent" <simonstl@simonstl.com>
- Date: Thu, 17 Oct 2013 17:35:36 -0500
Hi Simon,
I'll buy into your view on REST, maybe a better fit is something like Web Sockets? However, I can't agree with you in regards to tighter specs inside applications and looser between them. Are you suggesting that (for example) a Java method that has a single String as it's input and output needs a full XSD or some other more formal spec? I suspect you're indulging in a bit of hyperbole in that, flexibility between applications in what they can accept might simplify the world, but you know as well as anyone that not everything can be mapped to name value pairs or tuples and left at that?
- References:
- Transformative Programming: Flow-based, functional, and more
- From: "Simon St.Laurent" <simonstl@simonstl.com>
- Re: [xml-dev] Transformative Programming: Flow-based, functional, and more
- From: Peter Hunsberger <peter.hunsberger@gmail.com>
- Re: [xml-dev] Transformative Programming: Flow-based, functional, and more
- From: Uche Ogbuji <uche@ogbuji.net>
- Re: [xml-dev] Transformative Programming: Flow-based, functional, and more
- From: Peter Hunsberger <peter.hunsberger@gmail.com>
- Re: [xml-dev] Transformative Programming: Flow-based, functional,and more
- From: "Simon St.Laurent" <simonstl@simonstl.com>
- Re: [xml-dev] Transformative Programming: Flow-based, functional, and more
- From: Peter Hunsberger <peter.hunsberger@gmail.com>
- Re: [xml-dev] Transformative Programming: Flow-based, functional,and more
- From: "Simon St.Laurent" <simonstl@simonstl.com>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]