This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Expiration of Java Web application

 
sura Herath
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Team,

I have developed a web application using java technologies and I'm going to give it to my customer for evaluate the application. So before I submit it I need to put some mechanism that prevent customer using it for more that 30 days or 30 times. So its really appreciate if some one could provide me mechanism/solution for this.

Many Thanks,
Suranga
 
Siddhesh Deodhar
Ranch Hand
Posts: 118
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Simply keep two condition (30 days or 30 times) "OR"ed flag in your database or code.
 
Vijitha Kumara
Bartender
Posts: 3913
9
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
sura Herath wrote:...So before I submit it I need to put some mechanism that prevent customer using it for more that 30 days or 30 times. So its really appreciate if some one could provide me mechanism/solution for this.

Though there can be various ways to acheive this, solution may depends on certain things. How are you going to setup the parts of the system (i.e: Database, application server etc..). Are they in the client side which can be manipulated by the client? Is this 30 times means 30 requests for the application?
 
Vijitha Kumara
Bartender
Posts: 3913
9
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
And welcome to JavaRanch Sura
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic