Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Anyone could help me to understand this concept basic about DOM fromHTML, I saw in the documentation they say this :
The Document Object Model (DOM) is a programming API for HTML and XML documents.
For example the API from Google :
API Google
But because DOM is an API?
Anyone could explain because DOM is a API?
This is the article full :
What is the Document Object Model?
Editors
Jonathan Robie, Texcel Research
Introduction
The Document Object Model (DOM) is a programming API for HTML and XML
documents. It defines the logical structure of documents and the way a
document is accessed and manipulated. In the DOM specification, the
term "document" is used in the broad sense - increasingly, XML is
being used as a way of representing many different kinds of
information that may be stored in diverse systems, and much of this
would traditionally be seen as data rather than as documents.
Nevertheless, XML presents this data as documents, and the DOM may be
used to manage this data.
From here in w3
In the DOM, documents have a logical structure which is very much like a tree; to be more precise, it is like a "forest" or "grove", which can contain more than one tree. However, the DOM does not specify that documents must be implemented as a tree or a grove, nor does it specify how the relationships among objects be implemented. The DOM is a logical model that may be implemented in any convenient manner.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I want to build a ad serving platform like serving ads by words in the content. I want to make word as affiliated link. I have some campaigns with some tags words. When request comes to ad serving API it should serve suitable campaign for those words with some additional conditions. like device type and location etc... I've tried with Redis, couchbase and mongo but My API is not serving within a sec. please suggest me some database and how to design database.
The problem is probably not the database you are using but how the datais structured and indexed. Mongodb and Redis can both be as fast as it gets, as well as more traditional relational dbs for this problem.
If using mongo for example and you have a campaign documents with a field containing an array of tag words, you should index that field, and results can be very fast.
If I understand you correctly, you want to take some keywords and find an ad campaign that fits those keywords.
Eg. "car" and "texas" keywords might be used to find an ad campaign for car dealerships in Texas. Basically, you add the tags and find the best fit. Is this correct?
Couchbase has full text search capabilities. This is probably the most efficient way to query the database for word matching if you want to match multiple input words with a list of words stored with your campaign document.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am sorry if this is not a constructive enough question.. Coming from the SQL world I'm just trying to wrap my head around this. After reading a lot about MongoDB, I've become very enthusiastic about it and consider using it for an upcoming application (in combination with Meteor).
However, I came across this blog post, which describes the troubles Diaspora ran into when using it and states "you should never use MongoDB". The examples she's giving sound pretty convincing.
Are these true problems with MongoDB, or were they using it wrong? Is this article now outdated and are there better ways for doing what they're doing (duplicate data for instance, like users being linked to each other, to posts and to comments, is a very common use case)?
Yes, there is a plenty of cases when mongodb not feet good, some of them are
When data perfectly described with 'table' metaphor (better using
SQL)
When you need ACID and transactions out of the box
When your workflow extremely oriented to write operation
When you need to generate complex cross-data reports
Data model have strongly relational view (a lot of connected
instances)
There is a lot of others, but this is just something which comes to my head fast.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am trying to learn NoSQL, and am implementing that in a project I am working on now as a means to pick it up. I understand there are no hard rules around it. But I'd be happy to read on some of the following:
Guidelines on how to structure a NoSQL document.
Moving from a RDBMS to a NoSQL thinking.
Difference between storing data in a NoSQL to that from RDBMS
Thanks!
I do have previous experience in RDBMS, and have been working with them for years.
Every concept will require to learn new thinking. Your question is to general for a specific
answer.
You will structure and work with CouchDB documents in another way as with MongoDB documents. In CouchDB you will do queries with MapReduce. In MongoDB you have a flexible query interface similar to a RDBMS.
A Key-Value store requires a completely new way of thinking. You have to know your query patterns before you are able to structure your content the right way. You have no index, so you have to build your own structure.
One blog that gives a lot of NoSql information is http://nosql.mypopescu.com
Update
The Riak people have some interresting questions too:
Will my access pattern be read-heavy, write-heavy, or balanced?
Which datasets churn the most? Which ones require more sophisticated conflict resolution?
How will I find this particular type of data? Which method is most efficient?
How independent/interrelated is this type of data with this other type of data? Do they belong together?
How much will I need to do online queries on this data? How quickly do I need them to return results?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
CSDL includes elements Documentation/Summary and Documentation/LongDescription that, according to MSDN, can be used to document entities. The contents of these elements conveniently appear in the properties window of the entity design surface, so it is easy to jot a few notes in these fields as you're working with entities.
Since the EDMX file is XML, it would be easy to write an XSLT stylesheet to pull documentation from these elements. Is there a standard tool for doing this? Are there any other advantages to using the CSDL documentation fields? Is anyone using these fields, and if so, have you found them to be an effective way to document your entities?
The documentation data stored in the CSDL is emitted as XML doc comments in the generated code. As a result, it will appear in the intellisense tooltips in Visual Studio automagically:
If you want to use it for more formal documentation you can use SandCastle (optionally together with the excellent frontend SHFB), or some other Xml DocComment extraction tool to build windows help files or help websites containing the documentation.
If your database is documented using the documentation attributes in SQL Server, you can extract that documentation from the database and populate the SSDL and CSDL comments using this tool: http://huagati.com/edmxtools/
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
My team creates a lot of one-off web forms. Most of these forms just send an e-mail, and a few do a simple database write.
Right now, each form lives in its own separate solution in Visual Studio Team Foundation Server. That means we have close to 100 different form projects, which makes it difficult to maintain consistency. Each form is unique in that the fields are different, but all of them do pretty much the same thing.
I'm looking to condense these somehow, and I could really use some guidance
Should I try to create one solution file with all of our form projects in it? There isn't a lot of plumbing code, although I could create a few helper classes to help with e-mail formatting and such. It would be very helpful to be able to share CSS, JavaScript, controls and images across projects.
Given that we're a Microsoft shop, are there any tangible benefits to going with something like MVC over Webforms for this specific scenario? I am sold on the concept of MVC as a whole, but would it help me pull together a 15-field data collection form more efficiently if all that form does is send an e-mail? The form that got me thinking about this had a good bit of logic built in to show and hide fields based on the user's responses and seems like it would have been less efficient to use MVC and jQuery.