Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: markspace <-@.>
Newsgroups: comp.lang.java.programmer
Subject: Re: tools for programming applets
Date: Sun, 22 May 2011 06:05:57 -0700
Organization: A noiseless patient Spider
Lines: 37
Message-ID: <irb1nt$8fg$1@dont-email.me>
References: <028d2009-98b7-43a3-b02d-83eaa89db79e@glegroupsg2000goo.googlegroups.com> <ir9k0j$43r$1@speranza.aioe.org> <34a39063-043f-4f49-8fd8-944d2d795af5@l2g2000prg.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 22 May 2011 13:06:05 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="8FmyTa30jaHydmbsw/NXBQ"; logging-data="8688"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/UQHFd0tXkHhBaqemllQlJdcC2+0pdg5o="
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
In-Reply-To: <34a39063-043f-4f49-8fd8-944d2d795af5@l2g2000prg.googlegroups.com>
Cancel-Lock: sha1:dO6QskzRLeNHNs9Pv9wGt1BiJdg=
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4417

On 5/22/2011 5:30 AM, horos22 wrote:

> I guess I could use a little more detail here since I really am not
> familiar with applet development or programming.


What kind of programming are you familiar with?  It might help us point 
out where things are different.


> Do you have a good
> pointer to a decent resource on the subject, say for setting this up
> with apache?


Start here, especially the part about deploying an applet:

<http://download.oracle.com/javase/tutorial/deployment/applet/>


> My client that I'm going to be working on is totally separate from the
> server. Hopefully, I'm going to be doing development locally, and
> then, when done, uploading the code changes to the server. If there is
> a simple applet directive that I could put in a test page that could
> take the code from localhost and run it against data that is hosted on
> the server, then that is exactly what I need.


There really isn't.  I need to turn this around and ask: what "data" are 
you trying to pull from the server?  SQL?  Raw files?  Some other 
network protocol, SOAP perhaps?  Something else entirely?

I think we need to get beyond this "simple directive" nonsense and try 
to deal with the actual problem.  Direct routes are often the most simple.