9 messages in com.mysql.lists.javaRe: Connection from an applet
FromSent OnAttachments
Sohaila Roberts13 Nov 2001 17:17 
Yiu Wing13 Nov 2001 22:55 
Røman Olshansky14 Nov 2001 07:44 
Chris Gerrist14 Nov 2001 12:56 
Chris Gerrist14 Nov 2001 13:51 
Igor Fedulov14 Nov 2001 14:46 
Yiu Wing14 Nov 2001 21:32 
Yiu Wing14 Nov 2001 21:40 
Yiu Wing14 Nov 2001 21:57 
Subject:Re: Connection from an applet
From:Yiu Wing (yiuw@virgin.net)
Date:11/14/2001 09:32:54 PM
List:com.mysql.lists.java

Well, does it really matter whether you're using an applet OR a servlet OR a client-server application?

Yeah, it's more like a client-server application. Once the applet is loaded up on the client side, they can access to the same server as the web page as well as logging onto other databases and doing the other work. I have to say this sounds ambitious, but that's what I'd like achieve. So I'll have a database client that runs on a web browser, and it can log onto any MySQL servers regardless where they are.

If the it's an applet and it is already running on the client's machine, applet's are allowed access to the machines they were downloaded from. And if you can access the machine which the applet was downloaded from, you are 'God' (what I mean is you can access your DB server (e.g. a Connection object you created earlier and kept it in the session).

Sorry, I don't quite get your above points here. You're saying *applets* are allowed to access the machines they were downloaded from. And *I* can't access to that machine, right?

When you create the Connection object, don't you specify the IP address of your DB server? So, can you do it there?

Yeah, after I point my browser to the right URL to download the applets, I'll have to specify the IP for the DB server. So they're on a different server. Yeah, I think I'll try to do what other poster said - create a signed applet, but I don't know too much about it ;-(.

Thanks for your reply.