Search Results

Do both -- store them in a database initially. Cache them onto disk when requested. You get the best of both worlds -- easy transportable backup with scaleable distribution.

If the popularity of Ruby on Rails, Django and ASP.NET MVC have taught us anything it is that a clean, MVC-style web framework combined with HTML-like templating that has nearly full language access i …

In terms of what developers can do, designing the project so that one can swap out UIs easily without secondary effects or significant trouble will help a lot. Even better is if you can setup the proj …

Some sort of web service wrapper is definitely a good thought, but you should check the terms of the license to see how they define connection before pulling the trigger. Depending on how it is writte …

If you look around, most folks running PHP these days are running Wordpress, Drupal, Joomla and the like. Or one of 10,000 free, popular apps that pretty much work out of the box with a cheap PHP host …

Joe is pretty much dead wrong. Now, you can make the argument that you have one "clean" branch that represents the vetted, production-ready code. But not using source control until stuff is ready is f …

Widescreen monitors have really only taken off in the last 2 years -- they used to be the more expensive options. Design-wise, it has always been viewed that having a web page (document) go long so …

I think it is used alot more than you'd think -- the use is just below the waterline. There are many, many ruby on rails wrappers around thick, fancy java services. Especially when you start dealing w …

Most of the new front-end designs I've seen are doing a lot of this nowadays. It seems to work generally OK -- browser resamplers have got much better, pipes are fatter and images are heftier so you a …

Big kicker for anything with big scale is that if one is changing database schemas in some way, one typically has some big, nasty maintenance scripts to run. Now, these might take a second or so to r …

Doing the background service or task is correct tactic here -- web servers really are meant to serve brief requests not long running tasks. Best to keep those off the server. You also get the added ad …

99% of this really depends upon the answer to the question "if I updated the database, what part of the application would know who I am?" Typical web applications connect as a single user, the databa …

Your scenario has little to do with mobile web security and more to do with plain old fashioned remote access to stuff that used to be locked behind the old corporate firewall. So the same issues appl …

If it is html and JS then you do have the sources, or at least the important part of the sources if UI is your main focus, available to you -- just snag it using whatever browser tool you prefer. Hav …

There are some scenarios were I'd love to use dynamic CSS, but more often than not I'm stuck with using designers who need a bit of help understanding CSS basics. Throwing a dynamic language in the mi …