Home | August 2006 >>

Open source is too suspicious

People like and people are afraid of Open spurce

I found my observation interesting, so I'd share it with you. I have a demo version of one of my open source product hosted. So anyone can create an account and test drive the product. Registration is simple, however requires providing valid e-mail. So where is a catch? people think. Most of them trying the registration and leave non existing e-mail addresses. So what people are afraid of? Getting spammed from open source community? Asking for donation? Or what? It looks really funny, because the system is open source, so if you do not want to leave any e-mail, just install it locally and test. I had to add in a product feature of clearing invalid and not active accounts, so I even never see e-mail people left. Funny that people more trust businesses where they pay money. When you do online purchase you leave your valid address, but certainly company making business will sell your address or spam with own information. When people stop to be so naive?

Learning riding a bike

Saturday's bike trip to lake Chabot

I am not everyday cyclist, however my odometer shows many thousand miles. My bike is a road bike, it means it runs well on well road.; but It can run on not well road too. Actually my bike is hybrid, although it looks like a road bike, its wheels are a little wider, that makes it perfect for riding almost everywhere. So, the last Saturday I tried to ride my bike at lake Chabot. Beginning was pretty good, well paved road in woods, nice lake view. Some little up and down hills didn't bring me much trouble. Soon paved road ended, however the road was still good. Finally I reached some cross road where I should decide where to go. A sign shows some bike loop, however arrows pointed to some suspicious direction, a small bridge over the lake. I didn't hesitate and crossed the bridge. The is no any sign on other side, so which direction? One comes up a hill and other just directs back around lake. I selected around lake. Road became very bumpy and I had feeling that this way will bring me back. So, I decided to return and try a hill way. I quickly shift gears to get lowest one, but nothing helps. I couldn't push pedals and stopped. Weather became hotter and hotter. Hopefully I could walk my bike in shade of the nearest tree. I looked at rear cassette gear. It seems I hadn't reached limit, however my shifters can't move it on lower gear.

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.