I've built out a session service that contains a bunch of generic session information (e.g. stuff like username, current active alerts/modals, the area of the site they're in, etc). Effectively this serves the same use as $rootScope. Currently all this stuff is on a page load and rebuilt by a bunch of REST calls, which seems suboptimal versus just storing the session state somewhere.
I'm curious if people have weighed the pros/cons between serializing this session state out to a cookie versus putting it into a session object and sending it to a server. It would seem that for angular, which is quite client-heavy, storing it in the cookie has some nice properties: no latency, no requirement to accept arbitrary unformatted state info, etc. And design-wise things that are relevant only to the client stay on the client, which has good symmetry.
Has anyone tried it either way and has some advice about the downside/upside of either?