Hi Joe, Welcome to the Witango community.
Troy's comments about XML as a Database are quite valid on one key point - size. If...you knew that your data store would not be very big (less than a couple hundred simple records), then performance shouldn't be much of an issue. At least one method of Security to take for sensitive XML files, is to place them in a folder outside of the virtual directories of your website and use <@INCLUDE> or the File Action to read and write to them. The one big advantage you gain with this approach is the easy portability/deployment of your code and data. It's also possible to use 3rd Party COM or Bean Objects with Witango for your XML parsing if you're real serious about performance because then you could use SAX or a XmlStreamReader/Writer which can be faster than XML DOM. ---- As for your question about Java Deployment, which I haven't used myself, is that I know some people are using it - but that I believe it is technically still at the Beta stage, but it is close to the final release. Hope this helps. Cheers.... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xmlx.ca 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- > -----Original Message----- > From: Troy Sosamon [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 28, 2003 11:18 AM > To: [EMAIL PROTECTED] > Subject: RE: Witango-Talk: db vs. XML, and J2EE > > Joe, > > Using XML documents for a perminant database is not really a > good idea because you don't have the ability for indexes or > database level security. > The lack of indexes will cause performance problems when the > database gets very large. It will also put a lot of overhead > on the server because the whole file will need to be read > every time you want to read a record, however there may be a > way to cache it and just read it once. I am sure some of the > other developers on the list can discuss the ability to cache the db. > > I have no idea about question #2. > > Troy Sosamon > > -----Original Message----- > From: Joe Hardesty [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 28, 2003 9:24 AM > To: [EMAIL PROTECTED] > Subject: Witango-Talk: db vs. XML, and J2EE > > > Hello everyone, > > I am a brand new Dev. Studio user (still in the trial > period). My use for Witango will be to create a sellable > office manage app targeted to a very specific market. By > enterprise standards it will be a relatively small app, used > by small groups (less than 10 users). > > I have two question about implementing Witango applications: > > 1. For portability, I would like use XML documents for data > storage as opposed to using a dbms such as mySQL. Have any of > you tried this? > Compared to using a dbms, would the use of XML docs cause performance? > > 2. At witango.com, they state that Witango apps developed in Dev. > Studio can run on any J2EE server. Have any of you > implemented your apps on a non-Witango app server? Is it a > straightforward process? Are there disadvantages to not using > the Witango app server? > > Thanks in advance, and best regards for a great New Year! > > Joe Hardesty > Hardesty-Ingraham > Ephrata PA USA > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
