Re[2]: HELP: OS X Problem...
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29101
interpreted = N
texte = Note that [thisURL] relies on the webserver to provide it with the information, I believe, which means it will be different on different webservers. This is not a bug, but a difference in implementation. For example, Apache will pass through the completely digested physical path information, subject to all rewrite rules in effect. There are differences between IIS and WebSite that are similar; this is also why NT servers assume / means base with reference to WebCatalog binary rather than logical root of web site as on the Mac.ODBC is possible under Unix's; it is just not pretty. There will be other software that needs to be set up/purchased, in order to get ODBC working fine. I would actually recommend that SM integrate Perl support into WebCat, and use DBI to connect to databases rather than the much more limited ODBC.John Peacock ____________________Reply Separator____________________ Subject: Re: HELP: OS X Problem... Author:
(WebCatalog Talk) Date: 3/15/00 1:02 PMon 3/15/2000 8:07 AM, Eric Ridgley at eric@silvercreek.net wrote:> Let me put it this way: > Other than having a URL end in .db, is there any other difference I should > have in my WebCat Code when moving it from an OS 9 / WebTen / Apache server > to a OS X / Apache Server? It's my understanding that it should work > flawlessly. Is this correct? > I believe there are several issues. There is a difference/problem with some of the file related contexts such as movefile. I believe there is or was an issue with TCPConnect. This issue may be resolved. I believe SQL over ODBC is not possible. And I believe that the [thisURL] context does not work as expected, giving extended file path info that is not based on the server document root. There may be other issues. I'm sure that someone at SM will step in and correct me if I'm wrong. Instead, it would be nice to have a data page on the SM site that could be used as an at-a-glance comparison of platform/features and bug issues. Hint hint.Mike ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
| |
- Re[2]: HELP: OS X Problem... (jpeacock@univpress.com 2000)
|
Note that [thisurl] relies on the webserver to provide it with the information, I believe, which means it will be different on different webservers. This is not a bug, but a difference in implementation. For example, Apache will pass through the completely digested physical path information, subject to all rewrite rules in effect. There are differences between IIS and WebSite that are similar; this is also why NT servers assume / means base with reference to WebCatalog binary rather than logical root of web site as on the Mac.ODBC is possible under Unix's; it is just not pretty. There will be other software that needs to be set up/purchased, in order to get ODBC working fine. I would actually recommend that SM integrate Perl support into WebCat, and use DBI to connect to databases rather than the much more limited ODBC.John Peacock ____________________Reply Separator____________________ Subject: Re: HELP: OS X Problem... Author: (WebCatalog Talk) Date: 3/15/00 1:02 PMon 3/15/2000 8:07 AM, Eric Ridgley at eric@silvercreek.net wrote:> Let me put it this way: > Other than having a URL end in .db, is there any other difference I should > have in my WebCat Code when moving it from an OS 9 / WebTen / Apache server > to a OS X / Apache Server? It's my understanding that it should work > flawlessly. Is this correct? > I believe there are several issues. There is a difference/problem with some of the file related contexts such as movefile. I believe there is or was an issue with TCPConnect. This issue may be resolved. I believe SQL over ODBC is not possible. And I believe that the [thisurl] context does not work as expected, giving extended file path info that is not based on the server document root. There may be other issues. I'm sure that someone at SM will step in and correct me if I'm wrong. Instead, it would be nice to have a data page on the SM site that could be used as an at-a-glance comparison of platform/features and bug issues. Hint hint.Mike ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
jpeacock@univpress.com
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
searching for items that begin with a number (2004)
RE: creating writefile data from a nested search (1997)
RE: E-mailer error codes (1997)
'does not contain' operator needed ... (1997)
Fun with dates (1997)
Spawning Holdup? (2000)
Remove me from your list immeadiately (1999)
[WebDNA] securing passing info from php to webdna (2011)
Queertrons? (1997)
protect tag on NT IIS (1997)
WCS Newbie question (1997)
Variables for chat (1997)
taxTotal, grandTotal (1997)
Session Number (1998)
ftp to webstar (2001)
spreadsheet interface (1998)
Listfiles on network with NT (2000)
Quit revisited (1997)
page redirect in webDNA (1997)
[WebDNA] WebDNA restart script (2015)