In javascript do not pre-size the array, let it grow as it needs to by
adding on to the end as needed (javascript can do this). This way you will
not get all those additional trailing comma's.
In your servelt if you decide you do want to parse the string use the
StringTokenizer class.
what if they move your account to a different server causing your urls to
change to for e.g. www19.addr.com/~mgarde/somepage.html
Now aint that gonna suck?
-Original Message-
From: Monte Gardner [SMTP:[EMAIL PROTECTED]]
Sent: 31 October 2002 03:57
To: [EMAIL PROTECTED]
Subject:
I think that this is almost an impossible task. The only near
conceivable way, is perhaps by containing the information within a Java
Applet on your page. This would require a Java PDF reader, which would
then access the file from an undisclosed location, without any options
to save or print. But
A very very determined user can also find a way to intercept the stream
going to the applet in the browser and make a copy of it, so the stream
would need to be encrypted, however since the applet needs to decode it, it
will need to have the key, which imples that a very^3 user could decompile
Some containers allow you to set specific attributes for the session cookies. You
could set a cookie domain of .addr.com so that your session cookie will flow back to
any of the host names within a domain.
-Original Message-
From: Adrian Janssen [mailto:ajanssen;TRUWORTHS.CO.ZA]
Sent:
Yea I hear you. I think If I just make sure that the root page is
accessed with the proper URL, the rest of the relative URl's will
resolve against that one, so maybe I don't have to hard code all
of them. I'm still looking at the problem and maybe I'll find a more
elegant solution, but the main
Hans,
Thank you for the long detailed response. It helped confirm my gut
feeling that JSTL will make it easier both for junior and experienced
web developers.
By the way, I believe I found a typo in your article about SQL at
http://www.onjava.com/pub/a/onjava/2002/09/11/jstl2.html?page=3
You
Hi,
I'm working on an ecommerce application based on JSP/EJB. The problem that I have is
when the user clicks the checkout button multiple times, multiple requests are sent to
the jsp. I'm looking for a solution that is not based on javascript (basically at the
client side). Wondering if
hi,
If you don't want the request submitted a second time at all, you will
have to use javascript. Otherwise, there is something called sensitive
form resubmits and a relatively standard way of handling the situation.
You can find some info about it here:
Have a session bean that handles the checkout. If you synchronize the
method the user called, only the first call will go through while the others
wait. When the method is called by second one you can check to see if
they've already checked out.
You have to make sure to get synchronization on
Dror Matalon wrote:
Hans,
Thank you for the long detailed response. It helped confirm my gut
feeling that JSTL will make it easier both for junior and experienced
web developers.
Great.
By the way, I believe I found a typo in your article about SQL at
I don't know if this is any better then javaScript, but
you could write a small applet with a button which disables itself
after the first click. -- just a thought
--Monte Glenn Gardner
On Fri, 1 Nov 2002, priscilla augustin wrote:
Hi,
I'm working on an ecommerce application based on
Ok, having a flag set in the session and checking it before a checkout will
get me out
of doing the checkout more than once. But the problem I face here is, when
the browser
sends multiple requests, it always waits for the response from the last
request. But in my
case, the first request will do
When you check that they've already checked out, just send them to the
thank-you page.
- Original Message -
From: Augustin, Priscilla [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 01, 2002 3:11 PM
Subject: Re: Handling multiple form submits
Ok, having a flag set in
14 matches
Mail list logo
