Open GoogleCodeExporter opened 8 years ago
In version 1.0, there will be a "remote bridge" class which handles
communication between client and server Matlab instances. I think it's worth
flagging certain transactions in order to re-invoke them without re-saving all
of their data.
This might be limited to transactions with no return data.
This might look like an OpenGL display list or vertex array object, in that it
might make sense to flag transactions as long as a "remote bridge" instance is
in a "prepare fast transactions" state.
Original comment by Benjamin.Heasly
on 8 Jan 2012 at 10:05
The "remote bridge" referenced above is the new dotsClientEnsemble class. This
class implements an automateObjectMethod() method. This stores a method
invocation along with parameters in a list of named function calls. These
calls can be invoked by name. So when they're invoked remotely, only a small
amount of data (the name) needs to be sent via Ethernet.
This is already a win, since automateObjectMethod() can be called ahead of time
to "prepare" function calls to be invoked later.
It might be possible to figure out a way to optimize further, perhaps by doing
something clever on the server side. Maybe objects could be dereferenced at
"prepare time" and cached in a way that speeds up execution. I'm not sure what
this would look like. But the automateObjectMethod() API is in place to make
this possible without changing client code.
I'm going to drop the priority of this issue since I don't know what the
server-side optimizations would look like, or what the design criteria would
be...
Original comment by Benjamin.Heasly
on 5 Mar 2012 at 4:41
Original comment by Benjamin.Heasly
on 26 Mar 2012 at 5:22
Original issue reported on code.google.com by
joshiang...@gmail.com
on 18 Oct 2010 at 6:12