Abhilash KV
+************
abhilashkv@gmail.com
SUMMARY
- Diversified experience of over 8 years spanning across requirement capture,project planning,scheduling,design,development, implementation.
- Expertise in Windows SDK programming
- Expertise in socket programming
- Expertise in client-server applications
- Expertise in collaboration technology[application sharing,desktop sharing]
PROFESSIONAL HISTORY
- Microsoft India R&D Pvt Ltd., Hyderabad [July 2004 - till date]
- Sasken ,Bangalore [Sept 2003 - July 2004]
- Avenir [R&D of www.atinav.com NewJersey] [Sept 1999 - July 2003]
AWARDS/ACHIEVEMENTS
- Got Shipit award for win2k3 server in December 2005. [Microsoft]
- Gold star award for the outstanding performance in SFU in 2006. [Microsoft]
- Got Shipit award for windows Vista 2006 in November 8 . [Microsoft]
- A patent work in Laptop security is under processing [technical work done, under LCA scrutiny]
SKILLS
Proficient in : C/C++
Familiar with :C#,Symbian7.0,Perl,Java,VisualBasic
- OS :Windows NT/2003/CE/Vista/7,LINUX
- Libraries :WindowsSDK,COM,Xwizards,Xlib,Winsock
- Tools :Windbg,DebugView,PocketPCx86 Emulator,Megallan
EDUCATION
B.Tech(Computer Science and Engineering) from Regional Engineering College(NIT), Calicut(Calicut University)
PROJECTS
- Wireless WAN [Jan2007 - present]
Role : Analysis, Design and Implementation
Environment : Windows7,Windows Vista,Windbg
WWAN in Win7 provides a new wireless technology opportunity to deliver a truly Ubiquitous Connectivity platform and Out of Box Experience for “The Laptop OS”.
Ownership:
- WWAN MediaManager
- WWAN Connection Flow Engine
- Subsystem for Unix based Applications & SDK [Sept 2004 - Jan 2007]
Role : Analysis, Design and Implementation
Environment : Windows2003R2,Windows Vista,Windbg
This is Unix emulation on Windows.
Ownership:
- Windows Telnet for Longhorn
- Porting work for Vista Beta2 SDK both bsd and SCO
- Weakening of SCO libc\libm for x86/amd64/IA64 platforms.
- Utilities for Interix.
- 64 Bitisation of BSD/SCO utilities, Porting BSD libc for Interix.
- Bug fix on IDMU in R2 and LongHorn
- LUA work on windows telnet.
- Security work for telnet
- Porting work for Vista Beta2 SDK both bsd and SCO
- Implementation of ARM callable APIs [Nov 2003 - July 2004]
Role : Analysis, Design and Implementation
Environment : Symbian 7.0s, SDK 7.0, Code Composer studio
version 2.2, OMAP1510
This is an abstraction layer of inter-processor communication and multimedia processing block, to the application layer. The implementation is based on a design with a platform-independent application interface. Though, the application interface is fixed across platform, the implementation of the interfaces is decided to be platform specific for better optimization. In the current implementation Symbian running on ARM side of OMAP1510 is taken as the target platform.
Ownership:
ARM callable APIs
- Implementation of Mirror Driver [April 2002 - July 2003]
Role : Analysis, Design and Implementation
Environment : Windows98/2000/XP,Windows2000DDK,C++,
SoftICE,DebugView.
A mirror driver is a display driver for a virtual device that mirrors the drawing operations of one or more additional physical display devices. It is implemented and behaves much like any other display driver
In mirror driver we are attempting to catch the drawing operations at the driver level. For all drawing operations, the kernel-mode GDI would call mirror driver just like it would call an ordinary display driver. The mirror driver would ask the kernel-mode GDI to draw to a portion of memory that can be accessed directly by an ordinary application. Thus we get the data of all drawing operations in the specific memory created by our mirror driver. The user mode application can directly access this data from the shared memory thereby speeding the processing.
Ownership:
Mirror driver
- Application Sharing[ www.avecomm.com ] [Feb 2001 - March 2002]
Role : Analysis, Design and Implementation
Environment : Windows 98/NT/2000/XP,Linux,C++,Java, JNI
Application sharing allows you to collaborate with your audience through any desktop application regardless of whether the audience member has that application installed on their computer.Multiple applications can also be shared at a time.
Ownership:
- Desktop Sharing
- Application Specific Sharing
- Remote Sharing
- Annotation
- SessionRecorder/Session player
- Application Sharing for PocketPC[www.avecomm.com] [Oct 2000 - Feb2001]
Role : Analysis, Design and Implementation
Environment : Windows CE, Embedded Visual C++,PocketPC X86 Emulator,
Implemented a client for windowsCE platform for Handheld PC [ARM,MIPS,SH3] .So that low memory Pocket PC users can avail the high memory applications Especially applications reserved for higher end windows platforms.
OwnerShip:
Application sharing client for pocket PC
- Firewall solution using tunnelling[www.avecomm.com][July 2000 - Sept 2000]
Role : Analysis, Design and Implementation
Environment : Windows 98/ME/NT/2000/XP,Linux,C++
The purpose of this is to provide firewall solution to collaboration module ,voice over IP module and text chat module in aveComm SDK .ie,should be able to work behind firewall,HTTP proxy. The project comprehensively addressed all the issues posed by content filtering firewalls and there by making the Collaboration tool firewall friendly.
Ownership:
Tunnelling Module
- Voice over IP Module [Audio SDK, www.avecomm.com] [Jan2000 -June 2000]
Role : Analysis, Design and Implementation
Environment : Windows 98/ME/NT/2000/XP,C,Java,JNI.
VoIP (Voice over lP) in aveComm enables multiple users to have voice conversations over Internet in an efficient manner. It provides full-duplex voice functionality that supports multiple users and allows any number of people to speak via the voice module in the same way they would in a telephone conversation or conference call. Voice Conference brings an interpersonal dynamism to the site and applications, unmatched even by the telephone. Rules can be set in the system to enable/disable voice chat.
Ownership:
AudioSDK
- Conference Server [September 1999 - December 1999]
Role : Analysis, Design and Implementation
Environment :WindowsNT,Windows2000,WindowsXP,Linux,C++
The Conference Server is used to make possible the firewall behind users to participate in the conference. For two firewall behind user to communicate with each other there should be a central server. This central server is the CS.
In avecomm conference when a user who is behind firewall or proxy joins to a conference all users in that conference connect to CS. The CS then relays the data between those users. The relay will be based on subnet. That is it will not relay data between the users in the same subnet. But this feature can be disabled. That is relay will not be based on subnet. CS identifies the subnet using the source ip of the user. So if a subnet has two ip's, it will be identified as two subnets.
Ownership:
Conference server