Oracle Announces an In-Memory Technology, At an Ungodly Speed…And Cost. This article is from MemSQL so there is some bias towards Oracle, but they succinctly state how Oracle comes last to the table, then misses the ocean liner.
How should I send data? Well, it depends.
CSV: Use this whenever possible, any non-programmer will be able to use it. Works well for tabular data, if you included the heading as the first row, if the heading is in business terms. Easy to parse unless invalid or poorly escaped characters exist in your data. Difficult to validate. Does not work well for tabular or hierarchical data.
XML: Most programs can generate or consume xml. Some programmer skills are required of the user. The data requires a DTD or schema in order for the programmer/user to validate it. Easy to read, difficult to parse. Works well with any structured data, most unstructured data.
JSON: Can be parsed without a schema if the user has programmer skills. Find a library instead of using eval when validating or risk the vulnerability of hackers penetrating your program or system. Easier to do mashups because datasets can be modified, conformed, or extended. Good fit for structured or unstructured data.
Having trouble with connections to Oracle RAC? This useful article Local_Listener and ORA-12545 may help you solve the problem.