On Sat, Feb 25, 2012 at 1:30 PM, John Locke <m...@freelock.com> wrote:
<snip> > > I'd say the main difference is taking the standard centralized stuff one > step further than you've outlined, doing the URL parsing and establishing > conventions before handing off to individual web service controllers. > > I've also found it useful to have separate request and response objects, > though at the moment I don't recall why. And of course have a different > class for each type of response and request -- XML, JSON, HTML, etc. -- that > implement standard methods that the framework can call regardless of type. Ok. We'd need to map those out. Any specific ideas? > > > > I am also thinking the stuff we are doing with Moose will make this better > in the long-run. We can use the defined data structures there as both the > documented API and the basis for XML and JSON formats. > > > Excellent. Is this going to be available in 1.4? I expect that to be for customers, vendors, employees, business reporting units, and more for 1.4. It will depend on what I have time to do between paid projects naturally, but that's the minimum. Accounts and account headings might be too..... Chris Travers ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Ledger-smb-devel mailing list Ledger-smb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
