[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

rpc-reply fragmentation



Hi

I think we need rpc-reply fragmentation when the result of get or get-config operation is very huge.

Suppose I retrieve a route table which contains 10,000 routes. I have to wait for a long time until the device form a whole rpc-reply. If we allow rpc-reply fragmentation, the 10,000 routes can be returned in multiple rpc-reply. So I can see a portion of result rapidly.

What's your opinion?