# Accessing messages.properties on the client-side

**URL:** https://talk.openmrs.org/t/accessing-messages-properties-on-the-client-side/2710
**Category:** Bahmni
**Created:** [August 6, 2015, 4:44pm UTC](https://talk.openmrs.org/t/accessing-messages-properties-on-the-client-side/2710 "2015-08-06T16:44:29Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![darius](https://talk.openmrs.org/user_avatar/talk.openmrs.org/darius/32/8082_2.png) [@darius](https://talk.openmrs.org/u/darius)
#### Post date: [August 25, 2015, 6:57pm UTC](https://talk.openmrs.org/t/accessing-messages-properties-on-the-client-side/2710/18 "2015-08-25T18:57:40Z")

</div>

Spring controllers are beans, so a new one is instantiated on a context refresh. I don’t know if the classes are reloaded though, so it’s possible that static variables have their values preserved.

I would recommend that you generate the etag as a hash of all the message content. (Because as you have it now, a server restart (and maybe a module refresh) will require clients to redownload the whole thing. It would be preferable to only have to download 1.5MB if something changes.

---

_[View the full topic](https://talk.openmrs.org/t/accessing-messages-properties-on-the-client-side/2710)._