Hello Michelle, From what I see in your posts here and in our forums I think you don't really understand how exactly the DMXzone database tools and app connect framework work. I would like to clarify that for you and for the others reading this topic and your comments. First of all - no javascript runs on the server-side i.e. this statement is totally wrong in terms of explaining how the app connect framework functions: build dynamic websites (server-side and not client-side as the competitor Wappler) The whole dynamic data processing runs on the server-side depending on your selected server model (PHP, ASP.NET or classic ASP). So, let's say you are using PHP then all the database queries, joins etc. are being processed on the server side by PHP files and PHP functions (in this case PHP PDO). The idea behind our tools is to separate server-side code from the front-end. What that means? - It means that on the front-end you only use HTML, CSS and pure javascript. No <?php functions ?> are being inserted on the page. Then how do you get dynamic data on the page? - You then use App Connect Framework to call the data returned by the server-side code on the server and render it on the page. This is done via javascript. The results returned from the server are processed by PHP not "client-side". The only "client-side" part of the whole process is rendering the data on the page. But why do you do this? Why not just using <?php ?> code directly on my pages - it's how DW has done it for years and years! - There are many reasons to do this: Modularity & Reusability - With the application logic completely separated from the fron-end, you have a more modular web application. Your app logic can be reused by any number of web applications (sites) and on different interfaces. Responsiveness - In web applications using server-side code on the front end. (i.e. how DW server behaviors work) the workflow for a user clicking a button to get data looks like this: The user clicks a button to get the data Then the browser sends a request to the server Then the server queries the database Your code performs the logic Then it renders data in a view Then the server returns the response to the user Finally the user sees feedback after waiting the whole time for the page to load With separating client-side application, from the server-side processing you can take advantage of realoding only parts of the pages, which need to be reloaded. Also, as you have the data already returned from the server - you can do client side paging, sorting or filtering and not sending requests for every page change, or letter entered in the search box. What about the security? You say that: -Michele wrote For me, server-side solutions give me a feeling of greater security... Imagine that you <?php echo ...?> some data on a non-protected/non-restricted page. What would be the result? Everybody who has access to it will see the data rendered. Is it PHP to blame here, or is it user's fault as he didn't apply protection on his page? With dmxzone tools, the security is again applied in the server-side code, so it is the same. If you don't secure your data then it will be accessible. So the protection is always applied on the server-side and there is nothing to worry about ... Hope that clears the situation for you. As for the SEO concerns - nothing will change if you are using javascript front-end framework to render the data. What could cause SEO issues is the content quality actually, not the technologies you are using. Google doesn't care if you are using: <title><?php echo $row_recordset['WebsiteTitle']; ?></title> or <title>{{WebsiteTitle}}</title> In the code, when both get rendered by the crawler as "Fluffy kittens" Cheers, Teodor
... View more