L8V2L

... So process is the environment that the thread share and run in at any giving time. Right?Reading the definition, and understanding the concept is two different things. I understand what I read, but I need more to feel that understand-meant.

Including js. I'm using node --for the finaslly time Ingolme...I got to find that jar-- I plan to learn php along with SQL too--since they are like partner in crime--.

I'mma make this journey productiveful soon as possible. But I'll be learning for the rest of my time to come.

Hm... What of server side process and thread? Teach me Ingolme!

Ingolme, I'll put you in a bottle like a firefly... -- what horror is such a season to promote kids to chase after and catch little buys, and incapsulate them in jar -some with out holes for air-. And to leave them in there to suffer, starve, and die. What horror--... I did answer**ask** a question. Above the definitions.Those are just the definition. I'm asking for a use case, i.e. In Unix or Linux, or Solaris case. In the terminal.

/root/node/[node/@id = 1]

... My question still stand for clairty.

What's a process: In computing, a process is an instance of a computer program that is being executed. It contains the program code and its current activity. Depending on the operating system (OS), a process may be made up of multiple threads of execution that execute instructions concurrently.What's a thread:In computer science, a thread of execution is the smallest sequence of programmed instructions that can be managed independently by a scheduler (typically as part of an operating system). The implementation of threads and processes differs from one operating system to another, but in most cases, a thread is a component of a process. Multiple threads can exist within the same process and share resources such as memory, while different processes do not share these resources. In particular, the threads of a process share the latter's instructions (its code) and its context (the values that its variables reference at any given moment).

Thanks for the link, and being a good sport --did I use that in the right context--truth is I'm learning everything that comes my way --or at least try-- sometime I'll like to talk to others on what I'm learning, but have nothing to really talk about here, cause non of you are familier with node programming.Learning node proved to be not easy for someone who have no experience with server side programming concept, and there is no learning material that introduce node to you in a linear fashion --except for this one book I found... But it might change through out the chapters-- . But learning programming is never a linear expericence. The JSDG, MDN, and W3S does a good to great job at this. But MDN only speaks on it, there is no NDG --yet-- and W3S doesn't seem to want to do a tutorial on it.

Another respond to justsomeguy post I copy and paste:The answer to end all arguments.All database technologies (including your favourite one, including NoSQL), entail a series of compromises which make certain things easy and certain things hard.

None of them is me... But I'll send the link out like you said... I was hoping to see what justsomeguy would say.

Here the respond from what you wrote me that I post to the wizard of xslt:This is off topic for the XSL List.And the answer is that the person who wrote this has obviously never heard of XML databases. In fact he knows very little about databases at all if he thinks the only real database is a SQL database.Michael KaySaxonica It has different strengths.There actually _are_ large Web sites using XQuery in the backend, sometimes in conjunction with relational databases. There's no point in naming them to someone who has already decided the answers based on false premises, nothing could be better than his/her favourite technology!It is worth noting that XQuery/XML-native databases do not read XML in for each query any more than relational databases read CSV files off disk for each SQL query.Note also that IBM DB2, Oracle and Microsoft SQL Server all have XQuery support (to varying extents and in varying ways). The XQuery specification was edited by the co-inventor of SQL, and XML is based on SGML, which has a heritage going back to the 1960s. So?Liam----End----What you have to say to THAT! justsomeguy.On another note:quote name="justsomeguy" post="282463" timestamp="1408386193"timestamp! Unix!!!

:-( .... Why is there synch a large community for XML?I wish to be apart of that community, and be able to say I'm an XML programmer.I'm only using XML as a storage for my site information.I'm storing my user information in JSON. I can organize my JSON file that would better preform in action. Instead of having a large file of my user long in, i could break up that file. I'm not storing much information. Just things they'll like to maybe keep to look back on.If this becomes to much of a hassle, I'll see toward relational database. Or maybe a hybrid.I'll like to work with JSON and XML as my data storage for the use case of how I'll be using them.Plus I feel this will help me better myself toward html via XHTML.Oracles is one of the main database provider, right?And 28minsec --I believe that how it's spell-- and marklogic too, right?

Yes.... It's base on what your data is, and how you attend to use it.

READ/EAT THIS!I have been asked many times: What is faster, XML or Relational?. Of course, this question oversimplifies a complex issue, and so the only valid answer is It depends!. Sometimes people ask the same question in a slightly different way: If I have a relational table and convert each row into a small XML document and store these documents in a separate table with 1 XML column, whats the performance difference between the two tables (for inserts/updates/queries)?. But, in most cases such a conversion is not recommended and this type of comparison is, again, too simplistic.Lets say you want store, index, and query 1 million addresses and each address has a first name, last name, street, city, state, and zip code. Thats a simple and fixed structure and its the same for all records. Its a perfect fit for a relational database and can be stored in a single table. Relational databases have been optimized for decades to handle such fixed records very efficiently. However, if the application needs to convert the address data to XML format anyway, it can often be faster to store the data permanently in XML and avoid the repeated conversion from relational format to XML format in the application.Now consider a scenario where the business objects of interest are a lot more complex and variable than simple addresses. For example, derivative trades in the financial industry are modeled in XML with an XML Schema called FpML (financial products markup language). It defines more than 7000 fields (many are optional) with hundreds of 1-to-many relationships between them. Designing a relational schema to represent such objects is very hard and leads to hundreds of tables. The process of inserting (normalizing) and reading (denormalizing) a single object into such a relational schema can easily be 10x or 100x slower than inserting and reading a corresponding XML document in a native XML column (e.g. in DB2 pureXML).So, any performance comparison of XML versus relational depends heavily on which data you choose for the comparison, and what type of operations you measure.A large DB2 customer recently compared XML to relational performance because their business objects are currently mapped to 12 relational tables. Their application executes at least 12 SQL statements to retrieve all the relational data that comprises one of the logical business objects. Then the application reassembles the original business object. An alternative is to store these business objects as XML so that each object is stored as a single document. Instead of 12 tables, only 1 table with 1 XML column is then needed. In multi-user tests for data retrieval the the company found that the XML-based solution allows them to retrieve objects with 55% higher throughput than the existing relational SQL-based solution. The reasons for the performance benefit include fewer JDBC interactions between application and database as well as fewer distinct pages that need to be read when one logical business object is represented as one XML document (and not scattered over 12 tables). These tests were later repeated and verified at an IBM lab.Another important considertion in the question of XML versus relational is the data format in which the data is produced and consumed outside the database. If the data is produced and/or consumed in XML format anyway, it is often better to also store the data as XML in the database.So, the question What is faster, XML or Relational? is somewhat like asking What is faster, a truck or a ship?, because XML and relational are meant for different purposes, and either one can outperform the other depending on which use case you look at. And there are also use cases (with high schema complexity and schema variability over time) that cannot reasonably be implemented in a relational data model. (If you need to go to Hawaii, the boat always beats the truck!).The beauty of a hybrid database system such as DB2 is that you can use both native XML and relational capabilitues side by side, in a tightly integrated manner. Some data is better representated in relational tables, other data is better represented in XML, and you can manage both in the same database or even the same table, and with the same APIs and utilities.

... Yes.---that's when davej realize he was conversing with an idiotic. He set back in his chair, rub his eyes, and look toward the moon through his window. He spoke softly; "Alibell, when can I see you again my dear".---As I said, I wish to use XML database to store my XHTML pages information to Beale to manipulate them. And JSON to store my user information. That's my game plan.

So as soon as I open the page, the document is loaded with a variable referencing to it call document.Sax does not load the hold page in particular into memory before parsing it. Why didn't they go that rout?To bad sax is an api met for java.So yeah, since the site itself is under my control. I feel it would be safe to store it's information into XML. That way I can change the theme and display of it via xslt, instead having per defined webpage to load.I would rather store my data in JSON format, than relational --tubular-- format.I don't really know much about SQL, and I'm not driving to learn it.I found XML and JSON to be my choice for database store age format.If push comes to shave, and I'm getting more user than JSON can handle, than I'll look into SQL--but I doubt that, I believe JSON can handle the same intensety as tabulare database can--.

I ask for help from some other wizard to reply to this post buddy. So just you wait.In the mean time: so what about if I store my user data in JSON? And my webpage via XML to give me manipulation on how they are displayed.And.., when you use document.getElementsByTagName("p"); does this mean that the hold document is loaded first, and then the paragraph tag is extracted, or are we just using the already defined and load document in memory? --either way, it seem it'll have to be in memory as you said, but I'm just not all the clear on it-- If you'll be so kind as to proved clarity on this.

I can use couchdb than.

Thanks for giving this time. If you do get the time, please continue.

... No mongodb?What about a JSON database?As noted, I did say, I will like to use XML as a database to store my websites information --each individual web page-- that way I can configure it and shape them in different ways via xQuery and xslt.eXistdb a native database use xQuery as it's full querying language for accessing purpose.I could use a native XML database and or JSON native database. One to store my template for my web site, and another to store information on my users.How does that sound?

..... Yeah..... I... I am very fond of XML. The community is very large, as well as it's support. Other language have been built for it, and is xml base --meaning the language it's self is xml--.Yes, your right about the open and closing tag. I can see how that would be a problem for large database, but many of rage for XML to advance. The w3c pride it self of XML!Many could argue to you that xQuery is more advance than SQL.Why, if you do a quick search "xQuery vs SQL", you'll see favoritism toward xQuery over SQL.SQL is said to be here for times to come, and xQuery is not an replacement for SQL, but an alternative.To me, I see SQL as a language that's is part of php.But I have grown find of XML.If you do a search for xqib, you'll see attempts to making xQuery an alternative for js.I have read books to learn xml, xslt, xPath, xQuery, schema --DTD out of respect particle-- xPointer, xLink, etc.The only thing struggle with is choosing a database management system; either couchdb, mongodb, etc --there's a few others--What you said at the beginning about xQuery.. Maybe in 1.0. Version --and even in that version, it had the capability of doing everything that xslt 1.0 could do.XQuery to my knowledge exceed SQL very!Please give me information that will build me up toward my goal, instead of make me second guess my self on the language I have chosen.Add on of editing:I am ver shock to see that it was you Ingolme, that posted this.This would be something that davej would post.I thought you was the good one...

I didn't know you post this, I though it was davej. In this case, I will respond. You can query XML to that extant. xQuery.

There is a language for query object-oriented database. Definitively for XML!So I don't know why he would say that.I just... Would like to have a conversation --and learn from others-- I highly appreciate if you just want to type something to have other read it. I want to talk about things that is toward my goal; building a game website.I choose XML and JSON cause it's not hard to figure it out, when looking at it in its raw form.XML have a querying language that exceed SQL, and XML is in the format of html, plus it also have XSLT.I was considering of having XML hold the data that I will display in my web-page by transforming it via XSLT. And using JSON to store my user information.I have grown fond of XML, and desire to make my web page XHTML.Please give feedback davej.Even if you just talk on your database. Iron sharpen iron.

????.... If you say so.