Howdy! I wonder how on-the fly verification of e.g. credit cards or whatever else verification that could take some time can be done using Zope if Zope doesn't support multipart content. As a user I'd expect to get an immediate feedback like "verifying your credit card ... (please wait)" or "checking whether this domain name is available ..." and then after a while see the results without any further action. This is would be a typical job for multipart content-type, wouldn't it? Is there a workaround or so to get this done with Zope? Ragnar
Ragnar Beer wrote:
As a user I'd expect to get an immediate feedback like "verifying your credit card ... (please wait)" or "checking whether this domain name is available ..." and then after a while see the results without any further action. This is would be a typical job for multipart content-type, wouldn't it?
Is there a workaround or so to get this done with Zope?
I'd use javascript to display a message while waiting for the server to return the results. -- Tim Cook, President - FreePM,Inc. http://www.FreePM.com Office: (901) 884-4126 New MedicationManager, Try it now at: http://www.freepm.org:8080/FreePM
Unfortunately this is not possible, because we mustn't use JavaScript nor Java for the usual reasons. Pure HTML only. Ragnar
Ragnar Beer wrote:
As a user I'd expect to get an immediate feedback like "verifying your credit card ... (please wait)" or "checking whether this domain name is available ..." and then after a while see the results without any further action. This is would be a typical job for multipart content-type, wouldn't it?
Is there a workaround or so to get this done with Zope?
I'd use javascript to display a message while waiting for the server to return the results.
-- Tim Cook, President - FreePM,Inc. http://www.FreePM.com Office: (901) 884-4126 New MedicationManager, Try it now at: http://www.freepm.org:8080/FreePM
Hi,
Howdy!
I wonder how on-the fly verification of e.g. credit cards or whatever else verification that could take some time can be done using Zope if Zope doesn't support multipart content.
As a user I'd expect to get an immediate feedback like "verifying your credit card ... (please wait)" or "checking whether this domain name is available ..." and then after a while see the results without any further action. This is would be a typical job for multipart content-type, wouldn't it?
Is there a workaround or so to get this done with Zope?
Sure. Multipart only works with Netrape anyway. The most elegant solution so far is to use a so called meta-refresh <meta http-equiv="refresh" content="0; URL=http://anywhere/anything?anyparam=anyvalue"> It only works this way with this meta tag in the html-header. Using real http-header causes the browser to not load the page at all. So what happens? After submitting the form the user is immediately presented with this page which starts to load the next page at the same moment. This page shows as long as it takes to get answer from the next request. Almost like klicking on an ordninary link. Regards Tino Wildenhain
Hi,
Howdy!
I wonder how on-the fly verification of e.g. credit cards or whatever else verification that could take some time can be done using Zope if Zope doesn't support multipart content.
As a user I'd expect to get an immediate feedback like "verifying your credit card ... (please wait)" or "checking whether this domain name is available ..." and then after a while see the results without any further action. This is would be a typical job for multipart content-type, wouldn't it?
Is there a workaround or so to get this done with Zope?
Sure. Multipart only works with Netrape anyway.
s**t! I only tried with IE5 Mac not Windoze. Do you know about IE 5.5 Win?
The most elegant solution so far is to use a so called meta-refresh
The problem with that is the flickering. So I used it for redirects only so far. But maybe it's more acceptable with 5 seconds delay or so. [snip] Ragnar
Hi Ragnar,
Hi,
Howdy!
...
As a user I'd expect to get an immediate feedback like "verifying your credit card ... (please wait)" or "checking whether this domain name is available ..." and then after a while see the results without any further action. This is would be a typical job for multipart content-type, wouldn't it?
... The most elegant solution so far is to use a so called meta-refresh
The problem with that is the flickering. So I used it for redirects only so far. But maybe it's more acceptable with 5 seconds delay or so.
No. There is absolutely no flickering at all if you set it up like I mentioned. The browser blocks and shows the page with the meta-refresh until the server answers. With zope the servers answers only if all data has been created so its save. form -> server sends immediately the page with the meta-refresh with 0 seconds waiting. Only encoding the parameters in the URL or using session for this. The useragent then displays the page with the meta-refresh showing something like "please wait" and then connects to the server again, still displaying. Now the server begins the real work to check or calculate. If its ready it will answer the request finaly, resulting in an immediately display of the results. This works fine for us - we use it for long term database actions in our shop. Regards Tino Wildenhain
On Thu, Feb 22, 2001 at 06:22:20PM +0100, Ragnar Beer wrote:
As a user I'd expect to get an immediate feedback like "verifying your credit card ... (please wait)" or "checking whether this domain name is available ..." and then after a while see the results without any further action. This is would be a typical job for multipart content-type, wouldn't it?
Is there a workaround or so to get this done with Zope?
RESPONSE.write() -- Roberto Lupi
participants (4)
-
Ragnar Beer -
Roberto Lupi -
Tim Cook -
Tino Wildenhain