Re: Help needed!

This WebDNA talk-list message is from

1998

It keeps the original formatting. numero = 16497
interpreted = N
texte = John:Here's some thoughts.>(1) This customer would like to change his online databasefile every x >days. I would like to setup a 'maintenance webpage' for this customer on >which he can give a command to commit/close the database(s), so that he >can upload another file. Is there anything I should think of and is there >anybody who has any suggestions on how to do this the best way. What >about people coming in to the website just after closing the database and >before uploading the file. Is there a best way to go.Since customers to the site won't be changing the database (I assume), the best approach is to upload a new database file (as a safety precaution I usually rename the existing one then upload the new one), then execute the flushdatabases command, or, better yet, provide a link to a page that closes just the database in question. While the new database is being uploaded, the existing one remains in RAM and OK. When you execute the closedatabase, the RAM DB is flushed, and not written since it hasn't changed, and the new one read in.>(2) Dealers will be allowed in on a special site 'for dealers only'. I >would like to give the customer a possibility to add users to a specific >group (with access to the restricted site through the [protect groupname] >tag) through the same maintenance webpage. New dealers can then be given >permission on a per dealer basis. I know this should somehow be possible, >but I don't know how to go about. Again, it's one of my first websites >with WebCatalog.Yes, this is possible. I'd think a bit about this to make sure your don't give away too much access.>(3) I'm still having problems (while testing) with the Emailer >application. I get error messages number 151 with a timeout on the >connection with the mailhost. I'm running Emailer on the same PowerMac >9500/200 as EIMS and have no (performance) problems with EIMS whatsoever. >A suggestion was given some time ago to write directly to EIMS and not to >use the Emailer app, but this has not worked out to a working setup and I >have no idea if anybody got this working. Any help would be appreciated.Perhaps you could send me, via private mail to johnh@smithmicro.com, your mail host and I can try running emailer from here through it. There certainly shouldn't be any issues.>(4) Last question is that this customer would like to use cookies. Is >there anybody that has implemented cookies with WebCatalog 2.1 (Mac) and >would like to share some of his code with me or give some tips on how to >set it up. It's new for me and I would like to get this running like the >Amazon.com website where customers who return are known and don't have to >fill in any customerinformation. Through 1-click shopping they can order >easily.I know some people who are doing it. We've certainly tested pieces of this. Using the [setcookie] command and a special database for tracking the cookie values with the data should do the trick.John. John A. Hill, V.P. Marketing Pacific Coast SoftwareeCommerce / Web Developer Tools http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

Re: Help needed! (Jack Baty 1998)
Re: Help needed! (Sjoerd Jan ter Welle 1998)
Re: Help needed! (Sandra L. Pitner 1998)
Re: Help needed! (SIMS recommendation) (Christer Olsson 1998)
Re: Help needed! (SIMS recommendation) (Kenneth Grome 1998)
Re: Help needed! (John Hill 1998)
Help needed! (Sjoerd Jan ter Welle 1998)

John:Here's some thoughts.>(1) This customer would like to change his online databasefile every x >days. I would like to setup a 'maintenance webpage' for this customer on >which he can give a command to commit/close the database(s), so that he >can upload another file. Is there anything I should think of and is there >anybody who has any suggestions on how to do this the best way. What >about people coming in to the website just after closing the database and >before uploading the file. Is there a best way to go.Since customers to the site won't be changing the database (I assume), the best approach is to upload a new database file (as a safety precaution I usually rename the existing one then upload the new one), then execute the flushdatabases command, or, better yet, provide a link to a page that closes just the database in question. While the new database is being uploaded, the existing one remains in RAM and OK. When you execute the closedatabase, the RAM DB is flushed, and not written since it hasn't changed, and the new one read in.>(2) Dealers will be allowed in on a special site 'for dealers only'. I >would like to give the customer a possibility to add users to a specific >group (with access to the restricted site through the [protect groupname] >tag) through the same maintenance webpage. New dealers can then be given >permission on a per dealer basis. I know this should somehow be possible, >but I don't know how to go about. Again, it's one of my first websites >with WebCatalog.Yes, this is possible. I'd think a bit about this to make sure your don't give away too much access.>(3) I'm still having problems (while testing) with the Emailer >application. I get error messages number 151 with a timeout on the >connection with the mailhost. I'm running Emailer on the same PowerMac >9500/200 as EIMS and have no (performance) problems with EIMS whatsoever. >A suggestion was given some time ago to write directly to EIMS and not to >use the Emailer app, but this has not worked out to a working setup and I >have no idea if anybody got this working. Any help would be appreciated.Perhaps you could send me, via private mail to johnh@smithmicro.com, your mail host and I can try running emailer from here through it. There certainly shouldn't be any issues.>(4) Last question is that this customer would like to use cookies. Is >there anybody that has implemented cookies with WebCatalog 2.1 (Mac) and >would like to share some of his code with me or give some tips on how to >set it up. It's new for me and I would like to get this running like the >Amazon.com website where customers who return are known and don't have to >fill in any customerinformation. Through 1-click shopping they can order >easily.I know some people who are doing it. We've certainly tested pieces of this. Using the [setcookie] command and a special database for tracking the cookie values with the data should do the trick.John. John A. Hill, V.P. Marketing Pacific Coast SoftwareeCommerce / Web Developer Tools http://www.smithmicro.com John Hill

DOWNLOAD WEBDNA NOW!

Re: Help needed!

1998

Top Articles:

Related Readings: