Hello<br>Lately I've been experimenting with the feeder-api which seems like the right way to go. However, I do have a problem I am trying to understand.<br><br>The scenario is roughly this:<br><br>There is a file-server serving large media files (about 500 - 1500 mb each) and clients connect to this server requesting to download an image file. Nothing fancy really.<br>
<br>In the original implementation, the client connects, send a msg and the server replies with a series of ANS. The client gets a handle-frame callback for each ANS and stores it to some local storage.<br><br>I just tried to do this the feeder-api way. It looks like the server sends a series of ANS like it should but on the client side I never get any handle-frame callbacks, instead the client just grows in memory size so I assume it's queueing all recieved ANS.<br>
<br>I would appreciate some hints on ways forward to debug this. I don't need desperately it but its the right way to do it so I want to try to get it to work.<br><br>By the way, I don't use the supplied file-feeder, I wrote my own because the source of the media files isn't really the file system.<br>
<br>Regards and thanks for a great library.<br><br>/Martin<br clear="all"><br>-- <br>Martin Eliasson<br>+46 (0) 739 97 87 33<br><a href="http://asplunden.org">http://asplunden.org</a><br>