Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

I wonder what is the best way to change configuration after deploying the application. For example application may have to access a server to download some content. Obvious thing to do is to compile into the application default URL. It will work fine until URL doesn't have to be changed. When the server is moved somewhere else, application should be reconfigured in some way, for example:
1) user may be asked to reconfigure application manually... but seems to be bad idea...
2) I can send SMS message to the application which will change configuration automatically. sounds better, but it requires mainaining a database of users. May be difficult.

And also, when URL changes, I wouldn't like to resubmit the application for TRUE BREW testing again.

Any Ideas?

U can maintain a configuration file which will hold the necessary information such as server ip, port etc. On the start of application u can u can read this information and assign to the variables as necessary. U can also mainatain, alternate server ip and port in case regular server goes down. If you mainatin the application version also in this file it will be useful to update the file whenever required. For eg, u need to maintain the version both on app and server. Any request that you are sending from the app should also send the app version with it. If there is any mismatch in app version and server version, u can send the new configuration data from the server and update the configuration file. I had used this concept in most of the application that i have worked on. This concept works fine too. If any one has other ideas, lemme know :D

U can maintain a configuration file which will hold the necessary information such as server ip, port etc. On the start of application u can u can read this information and assign to the variables as necessary. U can also mainatain, alternate server ip and port in case regular server goes down. If you mainatin the application version also in this file it will be useful to update the file whenever required. For eg, u need to maintain the version both on app and server. Any request that you are sending from the app should also send the app version with it. If there is any mismatch in app version and server version, u can send the new configuration data from the server and update the configuration file. I had used this concept in most of the application that i have worked on. This concept works fine too. If any one has other ideas, lemme know :D

Yes, that will work fine, but I can see a problem here. Well I am just not sure, but as I understand the configuration file would be a part of application setup. In result, I won't be able to change this file after TRUE BRUE testing.

Yes, that will work fine, but I can see a problem here. Well I am just not sure, but as I understand the configuration file would be a part of application setup. In result, I won't be able to change this file after TRUE BRUE testing.

This should not be a problem, u can always update the information of that file say depending upon the version or some other criteria. The server should be able to send the update configuration data.
Regards
Arun Bangari

This should not be a problem, u can always update the information of that file say depending upon the version or some other criteria. The server should be able to send the update configuration data.
Regards
Arun Bangari

I think the best option and one we've used for other platforms is an application URL to pull down configuration data. The URL shouldn't change too often but when it does, just be prepared to go through testing with it.
Maintaining a database of subscribers can be quite hairy especially when you consider the licensing criteria, a subscriber one month may not be a subscriber the next so you would have to account for that not to mention inherant problems in delivering an MO SMS from within an enterprise to a vast (we can hope) subscriber base.

I think the best option and one we've used for other platforms is an application URL to pull down configuration data. The URL shouldn't change too often but when it does, just be prepared to go through testing with it.
Maintaining a database of subscribers can be quite hairy especially when you consider the licensing criteria, a subscriber one month may not be a subscriber the next so you would have to account for that not to mention inherant problems in delivering an MO SMS from within an enterprise to a vast (we can hope) subscriber base.

Well, and that's what worries me - initial URL :-) ... but looks like there is no alternative...

Well, and that's what worries me - initial URL :-) ... but looks like there is no alternative...