ash.MVC is a simple PHP programming framework proposed by Ash. The basic approach of this framework is to adopt a middle-path approach between faster development cycle, and a robust and scalable application. Moreover, the schemes proposed in the framework stick to the line of simplicity all along.
While encountering this new framework, ash.MVC, one may wonder with various questions, like:
- Do we need a framework at the first place?
- Why do we need another framework when there are numerous ones available?
- Why do we use MVC design pattern for this framework?
All the above questions have been addressed in the FAQs page.
The framework revolves round the concept of MVC design pattern as expected. There are four elements: 1. web browser, 2. Controller, 3. Model, and 4. View. These four elements interact with one another to establish a data-flow that is initiated by HTTP Request from client browser, and is successfully terminated with the receipt of HTTP Response at the client browser.
Typically, new software releases bear a version number such as 2.0. The version-numbered releases have new features and capabilities for one specific program. This is not the case with the latest round of 2.0s on the Web. They are a conglomeration of technologies, ideas, and approaches that, at least to some, represent a new way of interacting online. Their meanings are ambiguous and sometimes contradictory. In fact, one of the concepts of the 2.0 movement is being a movement away from new software releases.
Even though much of the 2.0 technologies are the playground for Web designers and programmers, knowing the terminology and sample sites allows the information professional to converse about the new trends and to find both useful sites and new capabilities to integrate into information products. Rather than debate the overall merits of the 2.0 movement, information professionals should explore the territory, techniques, and examples to find the most useful applications in your own work environment.
Read the whole story
Read the whole article
The beginning of Saturn is evolved from the passion to excel in the areas of futuristic Technology Solutions delivery. This passion through relentless brainstorming and hard work transformed as Saturn InfoLabs in the luxury of a 100 sq. ft. facility with a Home Computer and the great desire to deliver against all odds. The resolve to stay ahead, to explore, to ideate, to succeed, best define the concept of ‘SATURN’.
From it’s start up in 2003 taking up an innovative project implementation for a reputed regional Newspaper Group in India, we have come a long way to it’s present position of a leading IT organization with Technology and business achievements at par with the IT growth rate around the world. The company is now situated at Technopark, Trivandrum the biggest and greenest IT Park in India with CMMI Level 4 standard.
If you think you have a two plus years non-contiguous exposure in php/mysql with any of the Web 2.0 libraries feel free to drop a line to 91-471-3255001 for an appointment or forward resume to firstname.lastname@example.org. Please refer to this post, when contacting them.
Designing a database as part of a big project, will need a lot of experience. There are several factors which should be considered before finalizing a database schema. Since once the project starts rollout, there is no going back, other than adding a new index, or adding another field, any major change will affect the whole code base.
Indexing is the most important method you should try first for speeding up queries. Other techniques areÂ also available, but generally the one thing that makes the most difference is the proper use of indexes. On the MySQL mailing list, people often ask for help in making a query run faster. In a surprisingly large number of cases, there are no indexes on the tables in question, and adding indexes often solves the problem immediately. It doesn’t always work like that, because optimization isn’t always simple. Nevertheless, if you don’t use indexes, in many cases you’re just wasting your time trying to improve performance by other means. Use indexing first to get the biggest performance boost and then see what other techniques might be helpful.
One should take absolute care to optimize the fields by keeping in mind, that larger the indexes, slower the operations. The most common example of a mistake is to add a timestamp field to select the data in chronological order. Now if the total rows is just a handful, this wont be a problem atall, but if the total rows is millions, the timestamp field may have a cardinality of say 50% of the total rows, making the index very huge, and operations slow. But if instead of the timestamp, the data is stored in two fields with date in one, and time is another the cardinality of time will be 86400, ie the no of seconds in a day, and the cardinality of date will also be under control, making the operations faster by an appreciable amount. For varchar fields, creating partial indexes instead of full index helps, reduce the size of the index file, and hence give the server breathing space.
Hmm.. yes.. I literally meant it.. for several things you can directly use SQL calculations, though the queries and functions shown here are tested only with mysql, it should work with most other sql servers too. The cliche is if you have the sql server on the same server where your webserver and php interpreter is running. In simple terms, if you connect to mysql on localhost, sql can be used to a great extend to do calculations.
Some time back I did read on some other site, where two dates where calculated for the current month, using php mktime and date functions, to be passed in an sql query, for a range selection. I am not for an argument, but it seems more efficient to use the date calculations directly in the sql query, than pre calculating this unless otherwise it is needed to be printed in the output. Even then, the calculation can be done by the sql, and the result returned.
SQL calculations along with SQL session variables, will help a programmer achieve a very high optimization level for the scripts, thereby reducing webserver, and interpreter load.
Date calculations can use date_format, date_sub, unix_timestamp and from_unixtime and other related functions. Aggregates has all complimentary functions like sum, abs and others. By using a combination of these, any calculation can be achieved by sending an sql query.
The doubt on whether to use double or single quotes for static strings,Â has been a heated discussion on many a discussion groups. As of late I did a small bench mark, and has found that the encapsulation of variables in double quoted string is a slight higher load than concated string, even when the static string is quoted in double, whereas the most efficient is to specify single quotes for quoting static string.