Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

beginner in need of HELP!!!!!!!  RSS feed

 
john mattucci
Ranch Hand
Posts: 331
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
this is my scenario. Information is being sent to a
database ie MS SQL 7.0 (this info consists of several
dozen fields being filled in by clients). These forms
must then be divided equally amongst office admin people. I need an application which runs on a thread and checks every 5 min
if new forms have arrived; and then passing it to next admin
person. I would have a pointer to the last individual who
received a form. So everyone would obtain a fair share of the work. My question could this app be a Servlet(sorry i know very little about servlets)? If not what would be a better
choice? And last question could i drop this app on the SQL?
Just a little confused where the app would reside
Thank u very much for your time

------------------
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13078
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What is missing from your description is where the filled in forms are coming from - are these being POSTed from a web page? If so then it would be logical to add some sort of distribution mechanism to the servlet that verifies the form.
Also - do the workers pick up a new form via an http page or is there a separate application for processing the form?
Bill
 
john mattucci
Ranch Hand
Posts: 331
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
sorry i should have included more info. I will be using
Java Web Start to distribute the app. The application will
sit on the users desktop. And the office admin people will
have an app on their desktop, that will be reading the forms
from the SQL.
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I see no reason to use servlets at all. In your case it might be easier to just build a "fat" client. Do all of your communication through the database since you have few clients. So, just have all of the clients poll the database for new work, and if work is there, lock the appropriate rows until the client has obtained the data.
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
Tim Holloway
Bartender
Posts: 18662
71
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can't have a servlet run repeatedly on a timed basis, since servlets run in response to network (usually HTTP) requests. However, you can write a daemon process in Java that wakes up every 5 minutes (or whatever). *It* could make requests to a servlet via an HttpURLConnection, if you wanted it to.
If you're passing work, you'll need to have the daemon server notify users somehow - by sending a message to their machine (winpopup-style) or emailing or something, since there's no way to "push" content into a browser (and considering some of the most recent advertising techniques, I'm VERY grateful for that!).
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!