I've read through many of your posts here on T2W. First, I am not new to trading. Second, I am not new to trading forums. Third, I am an individual trader managing his own capital and not a paid shill for anyone, for anything nor for any reason.
Yours is not a problem of intellect, its a mere problem of slight narrow mindedness. I don't mean that personally - as many things can be taken out of context when reading one's writing on a forum such as this - I mean that in the context of having read many of your posts regarding (in specific) dbFX.
Did you actually read my post?
In my view (and I've re-read my own writing to be sure), it does not read like one who is being paid to write. It reads like one who has been lied to by yet another FX intermediary - is there anything new about that concept - I doubt it.
I worked at Oracle, when the Enterprise Software Industry was in fact, still, THE Enterprise Software Industry, before Silicone Valley turned into the virtual Software dust bowl that it is today. I worked in SV during the peak - at the boom of technology in this country. I was there, when things were really good - when Systems Engineers (pray tell) were making half a million per year, doing - well, Systems Engineering. I know Enterprise Technology. Many of the systemic systems running today throughout much of G100 and G1000 community are systems that one way or another, I had my hands on - in some fashion, either in part (mostly) or systemically. From financial institutions to hospitals, to the Federal government, to the U.S. Supreme Court, to DoD, to national retail chains, to aerospace, to higher education, to scientific institutions, etc., there are precious few mainstream industries and/or institutions whose IT department and/or Datacenter would be unfamiliar territory to me. Many sky miles still un-used.
What I can tell you about the systemic and simultaneous failures of both dbFX and FXCM at the Server/Gateway/Router/Network level on 1/23/10, would not be anything surprising to those that suffered through it - for they already know that what I've reported is true. What I find most interesting about the dual failure, is that it happened in the first place! No TRULY mission critical enterprise system should ever be exposed to a single fault interruption that cascades systemically - if it does, then it is not truly enterprise, nor is it truly mission critical and that bring up my next point.
If a business entity decides to enter the mainstream of a market that trades on average $3.4 Trillion per day (in the aggregate) where there is no central clearing (in the aggregate), that doing so absent a truly enterprise schema for hardware, software and network, is like playing Russian Roulette with the very deposits that make your business model work in the first place. But, that is a technical discussion for a different kind of forum, quite possibly.
My main point (jumping into the tail end of this thread at the last minute) is that dbFX should NOT ever LIE to me, or to any of its other customers. When I am told that my physical account sits on a physical server installed on the physical grounds of the physical building housing the physical business entity known as Deutsche Bank and that when I login to my physical account, that I do so through the physical Gateway (read: Firewall in most Corporate schemes) and to a physical Server owned, operated and maintained by Deutsche Bank, only LATER to find out (by way of a failuire) that my actual TCP/IP Network path is being routed through an FXCM Server (at any level of the logon sequence - regardless) - THEN - I realize that I have been LIED to.
Here's more proof:
I took a quick screen snapshot of the dialog box upon failure to login to the dbFX Trade Station. The first line reads: Cannot Connect to:
http://dbFX.FXCMCORPORATE.com server.
Open a windows command line by typing "CMD" off the windows primary menu: Run > Start. Type cd C:\ to get to the root. Then, from the root, type the string: Ping http:\\dbfx.fxcmcorporate.com (then hit enter or return).
You will obtain ping stats from a server called: 208.87.149.250. Now, for those of you with dbFX accounts, go logon to your dbFX Trading Station and let the application run. Then go back to the command prompt (c:\>) and type the string: netstat (while logged into your dbFX Trading Station).
This will show you a list of all your active network connections. Notice that somewhere in that list you will find the Server called: dbdemo.fxcorporate.com.
Now, from the root (c:\>) type the string: Ping dbdemo.fxcorporate.com.
What you will get is the IP address of: 204.8.241.13.
Now, note the difference between 208.87.149.250 and 204.8.241.13.
Next, go back to the root (c:\>) and type the string: tracert 208.87.149.250, then run the same string for 204.8.241.13. You will find that 208.8.241.13 will resolve to itself but BEFORE it does, the very last hop it makes is a system called: fxcorporate-gw.ip4.tinet.net [77.67.69.26].
That "gw" stands for Gateway, folks. And, that is how the cookie crumbles. When you logged into your dbFX "Server" you had no idea that you were doing it through an FXCM Gateway.
Thus, dbFX has no physical differentiation in its software, hardware and network technology, from FXCM. So, how on earth can they claim to be otherwise?
I'll leave that question up to the technology experts on this forum to decide.