On 4/6/12 14:27, Rick Hofstede wrote:
> Dear list,
>
> in order to retrieve backend data (by a frontend plugin), we currently use
> NfSen's communication
> socket. Although this works fine, basically, we have a problem when the
> transferred Array/String or byte
> code exceeds about 1012 characters. A closer look in NfSen's source reveals
> that the respective buffer
> sizes are indeed hardcoded to 1024.
Feel free to increase this limit to whatever you need. I was introduced in the
early days of NfSen in order
to prevent sending an infinite data stream to the backend. I will update that
in a next maintenance update.
- Peter
>
> Since we need to send more data to the frontend than is currently possible,
> we're planning to introduce
> a certain hex or byte code, to denote the end of a set of data chunks.
> However, this is not the most fancy
> way to solve the problem. Did any of you encounter similar issues and/or
> eventually found a solution?
>
> Best regards,
>
> --
> Rick Hofstede
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Nfsen-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
--
--
Be nice to your netflow data
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
