Recent content by the_whistler

I suggest you do your own research. Odds are around 1.5% max (if you dont have any wounds), which is a lot IMHO. Of course, only vaginal sex and being circumcised lowers the odds, but still ... You can read lots of messages on board from people who are worried to death and have to go through 3...

There are no official numbers, but estimates for the number of HIV infected prostitutes in Pattaya vary between 5 and 25%. It's a tremendous problem in Pattaya. Assuming you're not being extremely stupid and you're always wearing a condom, there's still a possibility it will break. You...

Hmmm I see I skipped some keys (like 66=D~ => TIF 68=NSDQ~ => route, etc), but whatever, finding out what's what is the easy part, of all this ;)

Just found the notes I made some time ago, maybe they're interesting to you (although it isn't exactly hard to find this out yourself, lol, since Sterling didn't bother to encrypt) -> [numberKey]=[value] 1=000238~ => packet length 2=0006~ => Packet identifier => 6 = order 3=XXXXX~ =>...

What exactly did you do ? You hooked some API functions in the DLL ? I did something similar, I created a little re-route of the incoming packet data, filter the packets for quote/order confirms etc, open up a socket and use this socket to communicate with my own program (I was also inspired by...

Bought anything yet ? I'm personally interested in this myself. I'm looking at Romania, where current prices are about about 0,15-0,20 euro/m2.

XP is not perfect. * The GUI just sucks big time. Compare it to a MAC or to Vista, just drag a window around the desktop and you see how hard XP sucks (also watch your cpu meter while you're doing that). Vista has its GUI based on DirectX, that's why it's so much better and everything...

Of course, but they can implement those risk management controls on their servers.

That would be MUCH better indeed. Still, I'd even prefer just a DLL, that would contain all needed function to connect to a server, send orders and would contain callbacks to my event handlers. I don't need interaction with the platform, that only means unnecessary extra delay's

I've explained that before: .NET can only interact with COM via a 'wrapper'. That wrapper translates everything at realtime, which will consume a lot of your CPU time. You can google for 'COM + interop + .NET' or read sites like these...

For the interested ppl: the reason why VB can handle so much more quote events/second is this: The 'WithEvents' keyword that's used in VB, ensures 'early binding' of the events, this means the compiler and linker optimize at compile time. This is also called 'static event binding' (...

Ok, did some more researching and found out that if you use the interface to create an instance, the property setting in Delphi becomes twice as fast. This is how I did it before: delcared order this way: order: TSTIOrder; Then instantiated this way: order:= TSTIOrder.Create(self); in...

Did some initial reverse engineering of my Delphi code. I found that it's using the same windows API (NdrClientCall2), but it calls it twice ! Apart from that, there's a lot overhead. Anyway, not sure yet why it's calling that API twice. Below is the important part of the Delphi disassembly...

I ran some new tests, this time I timed setting a property of STIOrder: STIOrder.TIF. When looping this 5000 times, I found on my setup: Delphi takes 22 seconds VB takes 14 seconds C++ takes 10 seconds I've reverse engineered the generated C++ code, I found that about all it does is...

I'm not using .NET, since it will use interop to translate COM messages which will result in a huge performance drop. If you have other idea's how to reverse engineer the COM stuff, please let me know (I'm good with ASM, but just don't know how to RE the COM events, since i don't know where to...