Re: Here we go again...
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66697
interpreted = N
texte = I think it is doable. WebDNA can wrap around any code, right? So you = should be able to use web service for grab the data and then parse the = data just like php. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Adam O'Connor Sent: Monday, April 03, 2006 1:52 PM To: WebDNA Talk Subject: Re: Here we go again... You can access tab/comma delimited data from other platforms, but can be = tricky. For me its easier to use a RDBMS. I have worked on projects=20 before where system software and web-based software both shared the same = data source - this would be tricky if the data source would have been=20 delimited data. Haven't thought of this before but can webdna utilize web services? So=20 if I have a .net server dishing out XML packets via SOAP/XML-RPC, can=20 webdna receive these packets and parse them? I know webdna can parse=20 xml, obviously, but can it interact with a web service? Perhaps it may=20 simple, never tried with webdna. Here's an example, I once had to grab data from an in-house db, MSSQL,=20 but the company would not allow web pages to be served from their=20 location/systems. But, they would allow web services, so I built a web=20 service via C# on their server, then used NUSOAP transmit the data and=20 parse into my php based web page. Bess Ho wrote: > Can you use WebDNA database outside WebDNA folder? > Are you required to use WebDNA to interect with WebDNA database? > How do you see the database relationship? > > Bess > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Pat McCormick > Sent: Saturday, April 01, 2006 6:43 AM > To: WebDNA Talk > Subject: Re: Here we go again... > > > Actually WebDNA doesn't use a flat file. That is the case for the =20 > older Typhoon version, but WebDNA, simply because it can have =20 > multiple databases open, is no longer a flat file system. > > The difference is that WebDNA doesn't formalize the structure of a db = > in any way. You are responsible for define a sku or key field and =20 > there are some nice tools to assist the process, like [cart]. =20 > Comparing that with SQL or Access, those products get more antsy =20 > about key fields, and field formats in general. They also enforce the = > idea of a database consisting of a collection of tables, which is =20 > also confusing nonsense. > > The purpose for products like Oracle, SQL and other "databases" is to = > encrypt your text so that you need to buy their products to see your =20 > text. Web-DNA is the un-database database. Create your own =20 > relationships. All key fields are optional. Structure your project =20 > any way you want, even using virtual databases ([table]), and to make = > it even better, keep all the data in plain text so you can x-ray the =20 > files at any time using any text tool. Ya gotta love that! > > > > > > > On Mar 31, 2006, at 2:12 PM, Bess Ho wrote: > > =20 >> WebDNA is using flat file for storing data. It is not a =20 >> relationship database like MySQL. Also once your flat file grow =20 >> beyond roughly 2 GB (check with Network Admin to verify the size), =20 >> you can't run data very well. The go-around solution is to break =20 >> down WebDNA database into smaller chunks for faster performance. =20 >> You really need Relationship Database for scaleable application. >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf = Of >> Kenneth Grome >> Sent: Friday, March 31, 2006 4:55 AM >> To: WebDNA Talk >> Subject: Re: Here we go again... >> >> >> On Fri, 31 Mar 2006 07:05:55 -0500, Terry Wilson wrote: >> =20 >>> ... you never know when you'll be required to start doing something = a >>> certain way; or at some point, an old solution just isn't good = enough >>> or fast enough any longer ... >>> =20 >> Example: >> >> A client of mine preferred webdna but his searches were too slow, =20 >> so he hired me to debug and fix them. His code was fine but the =20 >> database files were not configured to optimize webdna's =20 >> performance, so I could only recommend two options: (1) =20 >> reconfigure the databases (not a good solution because updated data =20 >> files came from another source frequently) ... or (2) switch to =20 >> MySQL and give that a try ... >> >> I really didn't know if MySQL could handle the task any faster than =20 >> webdna and I told him this, but he went for it anyways. He said =20 >> webdna hosting cost too much anyways, and since he wasn't committed =20 >> to using it on his server anyways (although he enjoyed personally =20 >> mocking up web sites because it's east for a non-programmer to use) =20 >> he decided to go with PHP and MySQL. >> >> The moment we switched his search times dropped from about 10 =20 >> seconds to less than two seconds. I think the reason is two-fold: =20 >> (1) he had database files that were too large for webdna to RAM-=20 >> cache efficiently, and (2) we were doing nested searches, and =20 >> webdna is pretty slow sometimes when using nested searches, =20 >> especially with large db files. >> >> The bottom line is that he "outgrew" webdna for use on his server, =20 >> and now he's happy again with a faster free solution. I think this =20 >> type of situation is going to become more and more common as webdna =20 >> continues to be less and less aggressively developed, supported and =20 >> marketed. >> >> Sincerely, >> Kenneth Grome >> >> owner@kengrome.com >> kengrome@gmail.com >> www.kengrome.com >> >> >> >> >> >> >> ------------------------------------------------------------- >> 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 > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> ------------------------------------------------------------- >> 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 > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> =20 > > > ------------------------------------------------------------- > 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 = > Web Archive of this list is at: http://webdna.smithmicro.com/ > > ------------------------------------------------------------- > 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 = > Web Archive of this list is at: http://webdna.smithmicro.com/ > =20 ------------------------------------------------------------- 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 = Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I think it is doable. WebDNA can wrap around any code, right? So you = should be able to use web service for grab the data and then parse the = data just like php. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Adam O'Connor Sent: Monday, April 03, 2006 1:52 PM To: WebDNA Talk Subject: Re: Here we go again... You can access tab/comma delimited data from other platforms, but can be = tricky. For me its easier to use a RDBMS. I have worked on projects=20 before where system software and web-based software both shared the same = data source - this would be tricky if the data source would have been=20 delimited data. Haven't thought of this before but can webdna utilize web services? So=20 if I have a .net server dishing out XML packets via SOAP/XML-RPC, can=20 webdna receive these packets and parse them? I know webdna can parse=20 xml, obviously, but can it interact with a web service? Perhaps it may=20 simple, never tried with webdna. Here's an example, I once had to grab data from an in-house db, MSSQL,=20 but the company would not allow web pages to be served from their=20 location/systems. But, they would allow web services, so I built a web=20 service via C# on their server, then used NUSOAP transmit the data and=20 parse into my php based web page. Bess Ho wrote: > Can you use WebDNA database outside WebDNA folder? > Are you required to use WebDNA to interect with WebDNA database? > How do you see the database relationship? > > Bess > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Pat McCormick > Sent: Saturday, April 01, 2006 6:43 AM > To: WebDNA Talk > Subject: Re: Here we go again... > > > Actually WebDNA doesn't use a flat file. That is the case for the =20 > older Typhoon version, but WebDNA, simply because it can have =20 > multiple databases open, is no longer a flat file system. > > The difference is that WebDNA doesn't formalize the structure of a db = > in any way. You are responsible for define a sku or key field and =20 > there are some nice tools to assist the process, like [cart]. =20 > Comparing that with SQL or Access, those products get more antsy =20 > about key fields, and field formats in general. They also enforce the = > idea of a database consisting of a collection of tables, which is =20 > also confusing nonsense. > > The purpose for products like Oracle, SQL and other "databases" is to = > encrypt your text so that you need to buy their products to see your =20 > text. Web-DNA is the un-database database. Create your own =20 > relationships. All key fields are optional. Structure your project =20 > any way you want, even using virtual databases ([table]), and to make = > it even better, keep all the data in plain text so you can x-ray the =20 > files at any time using any text tool. Ya gotta love that! > > > > > > > On Mar 31, 2006, at 2:12 PM, Bess Ho wrote: > > =20 >> WebDNA is using flat file for storing data. It is not a =20 >> relationship database like MySQL. Also once your flat file grow =20 >> beyond roughly 2 GB (check with Network Admin to verify the size), =20 >> you can't run data very well. The go-around solution is to break =20 >> down WebDNA database into smaller chunks for faster performance. =20 >> You really need Relationship Database for scaleable application. >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf = Of >> Kenneth Grome >> Sent: Friday, March 31, 2006 4:55 AM >> To: WebDNA Talk >> Subject: Re: Here we go again... >> >> >> On Fri, 31 Mar 2006 07:05:55 -0500, Terry Wilson wrote: >> =20 >>> ... you never know when you'll be required to start doing something = a >>> certain way; or at some point, an old solution just isn't good = enough >>> or fast enough any longer ... >>> =20 >> Example: >> >> A client of mine preferred webdna but his searches were too slow, =20 >> so he hired me to debug and fix them. His code was fine but the =20 >> database files were not configured to optimize webdna's =20 >> performance, so I could only recommend two options: (1) =20 >> reconfigure the databases (not a good solution because updated data =20 >> files came from another source frequently) ... or (2) switch to =20 >> MySQL and give that a try ... >> >> I really didn't know if MySQL could handle the task any faster than =20 >> webdna and I told him this, but he went for it anyways. He said =20 >> webdna hosting cost too much anyways, and since he wasn't committed =20 >> to using it on his server anyways (although he enjoyed personally =20 >> mocking up web sites because it's east for a non-programmer to use) =20 >> he decided to go with PHP and MySQL. >> >> The moment we switched his search times dropped from about 10 =20 >> seconds to less than two seconds. I think the reason is two-fold: =20 >> (1) he had database files that were too large for webdna to RAM-=20 >> cache efficiently, and (2) we were doing nested searches, and =20 >> webdna is pretty slow sometimes when using nested searches, =20 >> especially with large db files. >> >> The bottom line is that he "outgrew" webdna for use on his server, =20 >> and now he's happy again with a faster free solution. I think this =20 >> type of situation is going to become more and more common as webdna =20 >> continues to be less and less aggressively developed, supported and =20 >> marketed. >> >> Sincerely, >> Kenneth Grome >> >> owner@kengrome.com >> kengrome@gmail.com >> www.kengrome.com >> >> >> >> >> >> >> ------------------------------------------------------------- >> 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 > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> ------------------------------------------------------------- >> 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 > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> =20 > > > ------------------------------------------------------------- > 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 = > Web Archive of this list is at: http://webdna.smithmicro.com/ > > ------------------------------------------------------------- > 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 = > Web Archive of this list is at: http://webdna.smithmicro.com/ > =20 ------------------------------------------------------------- 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 = Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/
"Bess Ho"
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:
Search/sort in URL Was: GuestBook example (1997)
AppleScript/.db (was:FTP to WebStar) (2001)
URL for Discussion Archive (1997)
Dumb Question about Docs (1997)
Hierarchy of form/text/math variables (2000)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Release of 2.01? (1997)
WebCat2: Items xx to xx shown, etc. (1997)
Chown www:wheel Almost There WebCat 5 on itools 7 (2003)
searching problem (1998)
Nesting format tags (1997)
WebCatalog on Linux (2000)
More questions about serial number dishing (1997)
Formulas.db not working (2006)
Re:Change WebDNA-Talk Mail due to no digest for 1wk (1997)
WebCat2b12--[searchstring] bug (1997)
Bug Report, maybe (1997)
Need help with emailer- 2 issues (1997)
WebCat odd log behavior (1998)
Updating a database once per day - An example (1998)