[erlang-questions] RPC from linkedin driver
Thu Apr 2 16:55:43 CEST 2009
We are working on significant performance improvements and new API's for XMERL.
The new XMERL will be at least 4 times faster than the current
version. The base for this is a completely new
SAX parser that you also can use directly with new API's.
The memory consumption will also be significantly reduced.
/Kenneth Erlang/OTP Ericsson
On Tue, Mar 31, 2009 at 8:13 PM, Yogish Baliga <yogishb@REDACTED> wrote:
> I am currently working on developing a linkedin driver (c language) for XML parser (xmerl is too slow). This is a SAX parser is given the following input:
> 1. XML to be parsed
> 2. Call back functions (MFA) for start of node, end of node and for text elements
> I found C APIs to do RPC calls from c-node (ei_rpc). This require ei_cnode and fd parameters. That means I need to run the port as a c-node.
> Is it possible to do RPC from linkedin driver without converting linkedin driver as a c-node?
> -- baliga
> "The quality of programmers is a decreasing function of the density of GOTO statements in the programs they produce." - Edsger W. Dijkstra
> erlang-questions mailing list
More information about the erlang-questions