We are moving an Access based corporate front-end into a Web-based App [closed]
Closed 5 years ago.
Are there any conceptual drawbacks to building a web app with C++ and MySQL?
I’ve inherited a pretty interesting project where there is a good opportunity to take an existing piece of software and turn it into a SaaS web app. As the project is inherited, the code base/ framework is already defined as C++ and MySQL. The app itself is compiled and run as an EXE on Windows Server. The UI is web based and the app works as a kind of server. From what I do know of modern web apps, this is perhaps an unusual choice. These days, most people seem to opt for a PHP framework or Ruby on Rails. Certainly that is the impression I get from reading blogs on the subject. So, I’m very interested to know if a C++ EXE backed by MySQL is a solid foundation for a web app, or whether we should be looking to build in another way?
One page using querystring or many folders and pages?
I have an application where I have the ‘core’ code in one folder for which there is a virtual directory in the root, such that I can include any core files using /myApp/core/bla.asp. I then have two folders outside of this with a default.asp which currently use the querystring to define what page should be displayed. One page is for general users, the other will only be accessible to users who have permission to manage users / usergroups / permissions. The core code checks the querystring and then checks the permissions for that user. An example of this as it is now is default.asp?action=view&viewtype=list&objectid=server. I am not worried about SEO as this is an internal app and uses Windows Auth.
Revamp application [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 12 years ago. I am a software developer having an experience […]
Complexity of a web application
I am currently writing my Master’s Thesis on maintainability of a web application. I found some methods like the “Maintainability Index” by Coleman et.al. or the “Software Maintainability Index” by Muthanna et.al.
For both of them one needs to calculate the cyclomatic complexity. So my question is:
Web Frameworks caring about persistence?
I have noticed that Play! Framework encompasses persistence strategy (like JPA etc…)
How best to store images on a file system [closed]
Closed 8 years ago.
Is Web application a Web service?
According to W3C:
Drop in service for account management, authentication, identity?
I’m building an Android app and associated set of web services for uploading/downloading data. I need a basic (no frills) solution for account management (register, login, logout, verify credentials/token).
Servlet : Usage of Constants.java class vs context param
I’m just wondering whether to keep some of my variables in Constants class or keep it in web.xml