On Tue, 27 May 2014 15:54:59 +0200, Jiri Cincura wrote:
>
> 1. I do op_service_start.
> 2. Then op_service_info with isc_info_svc_stdin in items. That gives
> me 4b number (8k in my case).
> 3. Then I call op_service_info with isc_info_svc_stdin in SPB and {
> isc_info_svc_line, data length, data,
Trying to go to bare metal.
1. I do op_service_start.
2. Then op_service_info with isc_info_svc_stdin in items. That gives
me 4b number (8k in my case).
3. Then I call op_service_info with isc_info_svc_stdin in SPB and {
isc_info_svc_line, data length, data, isc_info_end } in items. And the
respon
Any guess why I'm getting "No request from user for stdin data"?
Should the data be sent to server in op_service_info message, right?
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
---
On Tue, May 27, 2014 at 12:09 PM, Alex Peshkoff wrote:
> Yes.
> We are moving (unfortunately slower than wanted) to make all numbers
> 4-byte in services. And therefore new place is made to use 4-byte format
> at once. That's not a very big trouble for you. The returned value is
> _maximum_, accep
On 05/27/14 14:02, Jiri Cincura wrote:
> Hi,
>
> I'm trying to implement restore via Services API when the FBK is on
> client (the new one from 2.5.2). The docs says:
> If service needs some data in stdin, it returns
> isc_info_svc_stdin in query results, followed by ***4-bytes value*** -
> number
Hi,
I'm trying to implement restore via Services API when the FBK is on
client (the new one from 2.5.2). The docs says:
If service needs some data in stdin, it returns
isc_info_svc_stdin in query results, followed by ***4-bytes value*** -
number of bytes
server is ready to accept from client.
The
