Guys, Im looking at the LiftResponse subclasses in net.liftweb.http, and I must say, the layout makes no sense what so ever! lol.
We have: http://github.com/dpp/liftweb/tree/master/lift%2Fsrc%2Fmain%2Fscala%2Fnet%2Fliftweb%2Fhttp%2FWsResponse.scala and http://github.com/dpp/liftweb/tree/master/lift%2Fsrc%2Fmain%2Fscala%2Fnet%2Fliftweb%2Fhttp%2FXmlResponse.scala I have the following beef with this layout: - The vast majority of the classes and objects defines in WsResponse are just bog standard HTTP response code wrapper, none of which are exclusive to web services. - XmlResponse also defines java script responses. Nice and obvious... ;-) Does anyone have any objections to me re-arranging like so: Moving all the generic HTTP response stuff like 401's, 404's, 410's etc etc to a file called StandardResponses.scala ? By definition, there is nothing special about these responses - they are part of the HTTP spec. Move stuff like AtomServiceResponse etc (xml based responses) into XmlResponses.scala, then move JavaScriptResponse into JavascriptResponses.scala This IMO, would be a much more sensible rational - JSON response stuff can also then go into the JavascriptResponses file. Thoughts? Cheers Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
