Archive for January, 2013

January 30, 2013 Leave a comment


A mobile back-end as a service (MBaaS) called Kii Cloud officially opened for developers today, boasting 25 million end users and a group of distribution partners, including NTT docomo. Kii Cloud, in development for the past two years, marries APIs and SDKs with a proprietary back end that abstracts the complexity of building servers.

MBaaS is more often a way to cater to developers. The idea here is that developers program the app and push it out to Kii Cloud without having to build their own servers and back end. At the crux of it, Kii sells simplicity and scale through the APIs and SDKs that use object database technology originally developed as an open source project by db4objects. Its ad network and distribution across Japan, Korea and China give it significant reach.

How Kii Works

Developers write code for its apps and deploy to Kii. The SDK provides identity services as a core capability…

View original post 533 more words

Categories: Uncategorized

January 28, 2013 Leave a comment

The Zinger

What makes working with WebSockets challenging at times is that the messages are extremely tiny and incredibly fast – making it hard to see them. 😉

With the updated Chrome Dev Tools,  you can now see the WebSocket traffic coming and going to and from your browser without using tools like Wireshark. Here are the simple steps to make the invisible visible:

1. Be sure that your Chrome version is 20+. At the time of writing this post (May 8, 2012), you need to get Chrome Canary or a fresh Chromium build.
2. Navigate to the Echo demo, hosted on the site.
3. Turn on the Chrome Developer Tools.
4. Click Network, and to filter the traffic shown by the Dev Tools, click WebSockets (all the way on the bottom).
5. In the Echo demo, click Connect.

6. Click on the left, representing…

View original post 128 more words

Categories: Uncategorized

January 26, 2013 Leave a comment

Bruno's Ramblings

I like node.js, and I’m not the only one, obviously! I like it primarily for two things: it is simple and it is very fast. I already said it many times but one more won’t hurt.

Before working with node, I had spent many years working with threaded application servers. This was fun sometimes but it was also often frustrating: so many APIs to learn, so much code to write, so many risks with critical sections and deadlocks, such a waste of costly system resources (stacks, locks), etc. Node came as a breath of fresh air: a simple event loop and callbacks. You can do a lot with so little, and it really flies!

But it does not look like we managed to eradicate threads. They keep coming back. At the beginning of last year Marcel Laverdet opened Pandora’s box by releasing node-fibers: his threads are a little…

View original post 2,832 more words

Categories: Uncategorized

January 25, 2013 Leave a comment

Thoughts on Software design and development

I was reviewing a code and came across something as
In this code client passes a month name based on which some logic is executed.

At first it might look as whats wrong? hmm ..what if in future multilingual support is introduced -the month names will be localized and the client supplies equivalant of “jan” in a language other than english –it will simply fail.This is a very simplistic use case, but hope I make my point

Never use data which can be localized as part of a business logic 

View original post

Categories: Uncategorized

January 25, 2013 Leave a comment

Technology Park

           Earlier, i have discussed many NoSQL datastores in my previous blog. Schema less datastores are really required to make the application scale at any point of time. MySQL can fits only up to small set of data. When the data grows up, its very hard to scale the MySQL DB by using shards/clusters. I opted to chose, MongoDB is one of the best key-value and schema-less store for the immediate migration strategy from SQL. Because, MongoDB is very ease to install. For querying the complex data, in other NoSQL DBs, you need to write a separate Map/Reduce program to segregate  your data. But in MongoDB, simply we can write the queries to analyze it.
Java Objects mapping with NoSQL data store similar to SQL ORM (Object Relational Mapping) using JPA. I am sure the developer will be more happier to use JPA in NoSQL. I found a…

View original post 291 more words

Categories: Uncategorized

January 23, 2013 Leave a comment

Job Tips For Geeks

Programmers often experience a high degree of frustration during the interview process, and one primary source of annoyance is how the programmer perceives the line of questioning or exercises.  In a buyer’s market where supply exceeds demand, hiring managers will often be a bit more selective in evaluating candidates, and talent evaluators may request or require more specific skill-sets than they would if the talent pool were deeper.  These tactics are short-sighted but deemed necessary in a crunch.

I recently stumbled on two articles with an identical theme.  “If Carpenters Were Hired Like Programmers” was written in 2004, and “What If Cars Were Rented Like We Hire Programmers” was posted very recently.  The tl;dr of these posts is essentially that programmers being interviewed are asked incredibly esoteric questions or are grilled about experience with irrelevant topics (wood color for carpenters, car wiring for car renters).  The…

View original post 797 more words

Categories: Uncategorized

January 23, 2013 Leave a comment

Learn soapUI - Open Source

In this series of Groovy blogs [numbered 10], i will be sharing very frequently  used “10 groovy scripts” which should be on your finger tips. These would come handy in order to perform any Automation using the Groovy in soapUI.

@Author : Pradeep Bishnoi
@Description : Collection of groovy script snippets required to achieve automation in soapUI

1. Using Log variable“Any Text message ” + anyVariable)

2. Using Context variable
 def myVar = context.expand( ‘${#TestCase#SourceTestStep}’) //will expand TestCase property value into the new variable
    context.testCase  // returns the current testCase handle

3. Using TestRunner variable
    testRunner.testCase // return the handle to current testCase

4. Using MessageExchange variable
 messageExchange.getEndpoint() //endpoint to the selected teststep
    messageExchange.getTimestamp()    //timestamp
    messageExchange.getTimeTaken()    //time taken to process the request/response

5. Using Project, TestSuite, TestCase, TestStep methods
def project = testRunner.testCase.testSuite.project
    def project = context.testCase.testSuite.project


View original post 141 more words

Categories: Uncategorized