Open source is too suspicious
People like and people are afraid of Open spurce
Learning riding a bike
Saturday's bike trip to lake Chabot
Ajax dilemma
Process on server or client?
Pushing most of processing on client side creates certain discomfort. Should I follow a rule like upload everything on client once, and download result back when a user everything finished. Yes, I know, for some application isn't possible to upload everything and some additional requests can be processed. But what approach to select if processing can be done on any side? Here is an example, I have a list of contact a user wants to sort or search. It's already on client side, so asking server for this work looks like overhead. But what if some user's request will require to do the same work on server side, like send e-mail to all contacts which name satisfy certain criteria? Should searching code be duplicated on server side, or a server can use client for that like create subprocessing on client when server do processing? What is your opinion?
Welcome to jAddressBook and Pebble integration
Have a jAddressBook account? Deserve to have a blog too!
Create jAddressBook account and get Pebble blog account for free! Did I mention that jAddressBook account is free? There is no SSO integration yet, just on account level, so your jAddressBook credentials automatically shared with Pebble blog system. There is a plan adding SSO and make switching between these two applications seamlessly. It can be a simple exercise for a student to get better feeling of web and J2EE technologies specifically. Interested? Let me know.