Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

System Design Question

Options
  • 05-05-2008 2:13pm
    #1
    information
    Closed Accounts Posts: 362 ✭✭


    Background:
    I have an intranet application.
    Part of it is a java desktop application deployed via Java Webstart.
    This app then communicates with the server using the http protocol,
    to do this I have to hard code the server address.

    Problem:
    I have this deployed in 50 companies.
    Every time I do an update to the system, I have to do a build for each company to change the server address, not a huge problem at the moment, but still time consuming.

    Question:
    Any suggestions as to how I could get the application to get the server address on the fly, so i don't have to hard code it.


Comments

  • Options
    #2
    Webmonkey
    Registered Users Posts: 9,579 ✭✭✭Webmonkey


    Have a fixed location that supplies the server address? and load it from there - or even store the server address in a file on the local machine and just update the text file rather than the server.


  • Options
    #3
    ressem
    Registered Users Posts: 2,426 ✭✭✭ressem


    Well JINI is designed for service discovery on a LAN.
    http://www.computing.dcu.ie/~davids/courses/CA464/week2.pdf

    --edit: wrong link pasted. This is someone else's code to do simple discovery by multicasting. --
    http://www.developer.com/article.php/10915_3728576_1

    for sample code for a client and server.

    Though the alternative of allowing the server address to be set in a JNLP xml <param> would make sense for autodiscovery pessimists like me.


  • Options
    #4
    information
    Closed Accounts Posts: 362 ✭✭information


    Webmonkey wrote:
    Have a fixed location that supplies the server address? and load it from there - or even store the server address in a file on the local machine and just update the text file rather than the server.
    Than would make the job even more time consuming
    ressem wrote:
    --edit: wrong link pasted. This is someone else's code to do simple discovery by multicasting. --
    http://www.developer.com/article.php/10915_3728576_1
    That looks like an option, might be a bit heavy weight if it has to be run every time tha app starts
    From link seems to match my requirements wrote:
    The client side of involved a little Swing app that ran on their desktop and interacted with the a network service. However, given the rather dynamic nature of our working environment, I didn't want to have to distribute an update for the client Swing app just because I had to move the service to a different host machine.
    ressem wrote:
    Though the alternative of allowing the server address to be set in a JNLP xml <param> would make sense for autodiscovery pessimists like me.
    Thats the solution I'm looking at, so when the server starts up at installation/update it would perform a one off hard code of the address that can be accessed by the app before it is deployed.

    cheers


Advertisement