Skip to main content

Can we store wifi and use it later?

I started using WIFI almost 8 years back (in 2006) when I moved to the UK. Before that, during the engineering degree I studied about WIFI energetically for achieving grades. Nowadays it’s a common friend and every day without her presence, it is awful to envisage. One day my data allowance on the mobile run out and I want to go to an event in central London and want to use the GPS. I had to take map printout and follow the route. I depend a lot on GPS navigation rather than a paper map. So I reached the location half an hour later in the event. Eventually I missed the event and while walking back to the tube station I was thinking about storing the WIFI somehow and using it later, like a battery. People might think why can’t I carry a portable modem and a laptop, but I am thinking about much sophisticated device than that like a battery for the phone.
Did anyone think about a life without batteries now? It is there since most of us on this planet born. In 1749 Benjamin Franklin first used the term "Battery". Ever since it started accruing and become part of everyone, from portable computing devices, mobile phones, electric cars and almost all the devices we are using today. For me the first memory is about a car that run using remote-control (gift for my cousin from his working abroad father).
Is it possible to invent a storage mechanism for WIFI? I don’t know, my connection with electronics is too poorer rather than using the electronic devices. But that day I wished if I have a device or a ‘mechanism’ to store the WIFI and use it later. Like the way mobiles/laptop/ ipad’s are recharging we charge the WIFI device in the  evenings and use it throughout the next day. Then we don’t need to worry about the big bills, these corporate mobile providers are sent at the end of the month.
Think about it and share your thought.

Comments

Popular posts from this blog

How to write secure mvc application using encrypting URL

There are lots ways available to write the secure Mvc application. In my experience I came across lots of secure application in public facing. I want to tell about some of the mechanism I followed. 1- encrypting the URL Parameters and preserving id's encrypted on the client side 1- I always make sure if I pass Id or any sensitive data into the view always make sure it's encrypted. By doing so make sure if we forced to use HTML.hidden or HTML.hidden for have the encrypted values, in action link if I pass any parameters from the client side (eg:- edit or create or navigating between different actions we can make sure that all the values are encrypted) During the design of the actions results if it's http get I usually encrypt the sensitive data [httpget] Public actionresult display() { TestModel testModel=new TestModel(); testModel.id= encrypt(id); Return View(testModel); } [httppost] Public ActionResult Display(string id) { Guid d_id= new Guid(decrypt(id));

Single page application (SPA) using ext.js

what is spa? Single page application are applications that fit in one page with rich and fluid user experiences like a desktop based applications. Why is SPA? All web based elements (html, CSS,javascript) are downloaded from the server on single page load and avoid the continuous page post back. i can explain what this mean. Suppose your web application is made of certain flow and it consists of 5 different pages. Each page need to get data from the user and save before moving to the next page. So when we navigate from one page to other it need to make a round trip to server to store the data in one page and get the data for the next page to display. but in spa we can avoid the continuous post backs. The whole page will not post back any time other than the first load. But it communicate to the server dynamically behind the scene and can achieve the same functionality. Spa using ext.js designing a SPA using ext.js is a challenging task if you are unaware about the ext.js

#saynotointerview for recruitment process

I recently went for a training that consists of employees from multinational corporations. During the brainstorming sessions, one fellow gentleman started speaking about firing his colleague. This guy is actually a senior manager and he interviewed the departed. He was blaming the unfortunate guy told he knows all the job description and he was smart during the interview. So they selected him for the job. But in the job, he never raised to his potential and they sacked him. The senior manager was claiming in the brainstorming session the decision was correct. But lots of people in training disagreed with that. Majority people told the recruitment or interview process in the company flawed to test that lad's knowledge. I strongly believe this might not be a one of the situation in recruitment? How many of you came across similar experience in your professional career? Do you believe the things we put in the job description are the exact things the potential employees will be do