Hi, as /Command currently doesn't contain /View component, I thought about creating some server, which would transfer image data to /View for the display.... Althought I could launch new /View task with --do "view layout [image %bay.jpg]" command line parameter, /View itself starts for some 4-5 sec on my P133, and it's not acceptable. So I thought about running /View and delivering data thru tcp/ip ports. So here's my question - what's the best kind of port to do so? open, open/binary, open/binary/direct, open/lines? To date the most used here is open/lines, but I would like to know also opinion of others ... The problem also is - if I will want to create some non-blocking server (e.g. something along the lines of Sterling's reb-proxy.r script), I will have to send data by chunks and then build the result on the other side). So let' say /View is making connection to /Command server, requesting instructions to do and I would like to send something like: "view layout [image <<<reduced image data here>>" ... Or is it better to generate the script-file? But then I would have to save image data and load it into /View from harddrive. I just thought delivering whole data thru tcp/ip port would be faster, but that's the question .. Anyone? Thanks, -pekr-
