Mature product :)

First time when I had faced with REFRESH_JMS_CONFIG_LIST RPC-command my thoughts were: what an idiot implemented this? What was the point to increase refresh interval upon failure? Why do not take advantage of application listeners and to not perform REFRESH_JMS_CONFIG_LIST call automatically upon JMS startup? But it seems that in 7.3 EMC has gone even further:

2 thoughts on “Mature product :)

  1. Pingback: Never happened before and happened again | Documentum in a (nuts)HELL
  2. Pingback: Q & A. XV | Documentum in a (nuts)HELL

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s