Hm, I hadn't considered localStorage for some reason. Some of the data is sensitive, so it might be a security concern, but it's worth checking out. Otherwise you should be able to create a service that accesses the child window and loads some data from it, right? The child window would have to store said data globally, which is bad but at least functional.
The backend is a legacy system, based around API calls (RPC-style, not REST). The ideal would be a WebSocket to the client, but I think I will have to keep it simpler to fit in the project's scope; reloading data stored on the clients on a set interval or when manually triggered by the user. Far from elegant, though. Thursday, January 16, 2014 1:28:20 PM UTC+1, Sander Elias wrote: > > Hi Mattias, > > Ok, that's the issue. if it's on 1 computer for 1 user, you can use > html5's local-storage to communicate between multiple instances. > However, as you have more then 1 system, you might as well solve it system > wide while you are busy with this. > What server software are you using? there are quite a number of way's to > let the server push messages to the client. Also the server know's which > 'screens' carry the same data, so it can push to those 'screens' only! > > Regards > Sander > > -- 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/groups/opt_out.
