[SOLVED] signed applet, or what

[AXH]

Hi,
I'm writing simple database program. It will be used only by company users (probably on lan). It's my first applet, but I though that embedding it on a web page, as an applet will be a smart move (no installation, configuration and updating problem for users).

I admit, I didn't do my homework, and was unprepared for privileges problems with database connection. Now I need someone more experienced to help me decide, should I change project to regular application, try to sign my applet (what to do, when certificate will expire? I probably won't even have contact with customer then), or is there any better way?

I just need some overview before I go any further.

[Nicholas Jordan]

I am working on the same problem today, first we need to know where the database is but as you say: "Probably will not even have contact with the customer." which given some of the help calls I have heard of is probably not a bad idea.

Think of it this way: Applet can talk to server it came from all it wants, codesigning and sophisticated authentication are such that if the client could do them, they probably wouldn't need you to write code for them.

Primary issue I see in assisting you is where the database is running at.

[AXH]

Thank You for quick answer, I'll try to convince them to set the applet on the server which runs database. If I understand correctly, that should be the best solution

If that will be possible, should I be prepared for some server configuration issues?