OTOH, allowing 'the public' to update infromation on your
server is a dangerous proposition - will this applet be
available on the big bad internet, or a nice 'safe' little intranet?
Andrew T.
Well, my applet is a quoting system. Agents will be able to log in on a
secure site and get a quote for their customers. I want the quote to be
saved to a database so that the underwriters at my company can see the
quote for reference (it's a liability thing). On the internal side, my
underwriters have an interface where they can add quotes, delete
quotes, and modify quotes with notes and such. What I originally did
was send the data from the quote that the agent got and sent that data
to the internal interface. My internal interface has about 4
subclasses, one of which it calls to save the file each time the
interface is opened. I originally sent the online data to that
interface and attempted to save the quote in the same manner as one of
my internal underwriters would input a quote.
Does that make any sense?
Security isn't easy to get right. If this is for a "real" business, and
hiring a consultant or another developer. Otherwise, you risk allowing the