You don't need a driver for this task. Use packet sniffer library like PCap (actually you'll need WinPCap ). It's really simple to capture packets and print them to console.
You don't need a driver for this task. Use packet sniffer library like PCap (actually you'll need WinPCap). It's really simple to capture packets and print them to console.
Alternative way is raw socket. But desktop Windows (as opposite to Windows Server) limits raw socket functionality.
I wanted to get to the packet before 'windows' does, im interested in high frequency trading and so I wanted to try and program really low level. Now that I have said this, does it make sense still writing a driver? – user997112 Oct 26 at 20:20 PCap is really low level because it provides a driver you're trying to implement, along with interface to user-mode applications.
Why to do this again? – Andy T Oct 26 at 20:22 I didn't realise, I thought winpcap was a wrapper with lots of excess functionality which would make things slower. So do you think (assuming they're working in C or C++) the guys developing HF trading platforms would use pcap on linux too, because it would be pointless to write a driver?
Or is there some performance guy by using a driver? – user997112 Oct 26 at 20:30 Yes, it can be used on Linux too. Yes, there's a big difference in performance writing own driver or using pcap, but I mean development speed ;) Probably a fact that people snifs heavily-loaded gigabit networks using PCap will convince you PCap is good enough.
And it has a priceless feature - filtering capability. It's a great deal to implement it yourself. – Andy T Oct 26 at 20:38.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.