Suppose you have developed a solution and will deliver the system within a few days. But you are not sure whether your client will pay you the rest of the price of the solution. So you want to develop a mechanism where your code will run upto 30 days or upto a fixed date or day-length. What are the options you can do as a developer? Possible Answers I thaught Of
Developing a key based solution and the system will ask for the key every 30 day. [but how should I do it? ]
Provide an XML file and the system reads some texts from the file before starting the modules of the application. In that XML file supply the date-range as validation logic. [But client may find the xml file and manually increase the date ]
Other standard industry practice from all your experiecnes. [This is what I am waiting for now ]
Ashik Uzzaman Senior Software Engineer, TubeMogul, Emeryville, CA, USA.
Read the time from a time server (not the local machine time, which can be set back), and when you detect the due date, pop up a reminder to pay and exit. The client must be connected to Internet for this solution to work, of course. Eugene. [ April 03, 2003: Message edited by: Eugene Kononov ]
Time Server? Well, how should I build a time server then? That time server I guess will take time the server machine... But I need to provide this mechanism in a non-web client/server solution developed in Swing. Then what may be the other options? Any light please! :roll: [ April 05, 2003: Message edited by: Ashik uzzaman ]