> > Regarding a single REST api called mezzanine.api.... that's how I would do > it and I consider myself a pretty smart guy :)
There is absolutely no reason why you can't generalize model serialization / deserialization and include it in the base of Mezzanine. With how common it is becoming it is almost a necessity. Questions? Does a rest api, in your vision, provide for parsing JSON content from the body of the http post? The standard rest concepts rely on the data being in the URL, but most often, with things like angular, you are posting JSON content in the body of the http message. Another thing to consider is web sockets. More and more event driven applications are becoming more popular. Pushing events from the UI to the server and back is really the future of web design. Angular doesn't do this for you, but it provides a framework that makes communication to the back end VERY easy to accomplish. Thoughts? -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
