On 27.03.2014, at 09:12, [email protected] wrote: > 2. Are there any other backend implementation that we need to consider?
You might want to consider websockets as most modern browsers support it already, http://caniuse.com/#search=websockets. It is not as simple as REST on both the frontend and backend however it offers the ability to push messages to clients which can be of help in locking or updating the status of records to avoid editing conflicts. It also allows you to pursue an RPC-style interface to your backend instead of forcing you to map your backend to REST verbs (GET, PUT, POST, DELETE) and all the theoretical discussions that that involves. Finally, the argument might be made that websockets better conceal the data moving back and forth between browser and http server. Show your boss the web-developer console of Firefox or Chrome and how you can see the JSON data being transferred back and forth - he/she might be surprised. :-) Karl -- Ostendorf Software https://ostendorf.com/ tel: +49 151 1270 4213 mailto: [email protected] -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
