2 posts tagged “mashup”

Continuing on the previous post of comparing the onelineweb framework to Blazeds and Graniteds here is the summary of why an internal framework is developed.

  

1 - Scalability : It was impossible to introduce the plug-in architecture without creating/changing the class loading of graniteds and ibatis. The end result would have been a large monolithic package instead of smaller modules.

2 - Multi client support : Browser, Windows Mobile, Blackberry, Mashup API(XML API) and distribution (Ex. RSS feeds, Outlook).

3- Multi server support : Client interfacing with multiple server components directly - search engine, content engine, application all in unified fashion. The xml way..  Spitting out xml directly from search engine or content engine instead of proxing via the flex server side component.

4 - Performance : Fast response time moving out all intermediate data exchange layers and natively compressing the data from database layer (right out of the resultset object) to gain speed at network layer using apache native compressors and browser native decompressors.

5 - Lightweight : Less dependencies on 3rd party libraries.

Let the problem define the framework rather than the framework defining the solution. Simpler is Better.

I was recently into the salesforce event arranged at Bangalore Hotel Ashoka. The food was great :)  The person sitting behind us introduced himself and said I am an anti-salesforce. Woh.. That was my opening conversation at the event. Well, I asked him why is he here then?? His answer was his BOSS sent him. Next question from he, why he hates salesforce?

This time the answer was really interesting. Most of their sales are made through the phone. What ever the phone conversation they are doing over phone, they are again typing that in the salesforce application. Additional  nuisance . I understand it is good for company, the boss wants to have the complete picture. But immediately it is an additional nuisance.

Now I am not going to talk here about the rest of my evening. I am going to highlight on this particular point.

Long ego, when I was developing a pocket PC application at Fidelity, I came to know few sales agents record the conversation and then use Dragon speech recognition to get the text.

Why not a mashup of phone to application which shows a filled up form based on your conversation. Finally, no nuisance to end users ;)