Comments on: Server-Push JPEG Stream http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/ The Eccentric Logic of An Eclectic Mind Sat, 21 Jan 2012 02:58:06 +0000 hourly 1 http://wordpress.org/?v= By: Adrenaline Hack | Adrian Hoe’s WebLog http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/comment-page-1/#comment-17466 Adrenaline Hack | Adrian Hoe’s WebLog Tue, 25 Sep 2007 06:39:35 +0000 http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/#comment-17466 [...] Server-Push JPEG Stream [...] [...] Server-Push JPEG Stream [...]

]]> By: Zhang Wei http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/comment-page-1/#comment-16865 Zhang Wei Tue, 18 Sep 2007 08:01:46 +0000 http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/#comment-16865 That's interesting. I am glad you have found a solution. Do you have any idea why Read_Some does not always read in 512 bytes? 张薇 That’s interesting. I am glad you have found a solution. Do you have any idea why Read_Some does not always read in 512 bytes?

张薇

]]> By: Adrian Hoe http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/comment-page-1/#comment-16551 Adrian Hoe Fri, 14 Sep 2007 13:35:07 +0000 http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/#comment-16551 Yes! I was having the same thought and just got it all hacked and corrected. I have a Data of 512 bytes in size. AWS.Client.Read_Some will not always read 512 bytes. When it reads less than 512 bytes, say, 500 bytes. Stream_IO.Write will always write 512 bytes. That means 12 bytes of garbage will be written after the useful 500 bytes. I got around with that by writing to the next index of the last byte read. So I did this: <pre> <code> Ada.Streams.Stream_IO.Write (File_Handler, Data, Index); Index := Index + Ada.Streams.Stream_IO.Positive_Count (Offset); </code> </pre> Yes! I was having the same thought and just got it all hacked and corrected.

I have a Data of 512 bytes in size. AWS.Client.Read_Some will not always read 512 bytes. When it reads less than 512 bytes, say, 500 bytes. Stream_IO.Write will always write 512 bytes. That means 12 bytes of garbage will be written after the useful 500 bytes.

I got around with that by writing to the next index of the last byte read. So I did this:


      Ada.Streams.Stream_IO.Write (File_Handler, Data, Index);
      Index := Index + Ada.Streams.Stream_IO.Positive_Count (Offset);
]]> By: 潜龙在天 http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/comment-page-1/#comment-16550 潜龙在天 Fri, 14 Sep 2007 13:27:35 +0000 http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/#comment-16550 Hi Adrian, Nice to hear that you are hacking again! Are your sure you are writing exactly the number of bytes read? Happy hacking! :D Hi Adrian,

Nice to hear that you are hacking again!

Are your sure you are writing exactly the number of bytes read?

Happy hacking! :D

]]> By: Adrian Hoe http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/comment-page-1/#comment-16514 Adrian Hoe Fri, 14 Sep 2007 07:43:40 +0000 http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/#comment-16514 Hi Zhang, I don't think so. It is a single stream and I think the socket layer of the OS has already taken care of the read-write-wait. Thanks for the suggestion. I will investigate into your suggestion and confirm what is contributing to the corrupted JPEG images. The problem I have at hand is that I don't have a video server running and I am connecting to a 3rd party video server given as a reference in the NDA. Again, I am quite limited to open discussion because of the NDA. Unless, I have the access to the video server, I can download those images directly from the video server based on the time to run a diff against the stream I obtained from my program. Hi Zhang,

I don’t think so. It is a single stream and I think the socket layer of the OS has already taken care of the read-write-wait. Thanks for the suggestion. I will investigate into your suggestion and confirm what is contributing to the corrupted JPEG images.

The problem I have at hand is that I don’t have a video server running and I am connecting to a 3rd party video server given as a reference in the NDA. Again, I am quite limited to open discussion because of the NDA.

Unless, I have the access to the video server, I can download those images directly from the video server based on the time to run a diff against the stream I obtained from my program.

]]> By: Zhang Wei http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/comment-page-1/#comment-16512 Zhang Wei Fri, 14 Sep 2007 07:31:42 +0000 http://adrianhoe.com/adrianhoe/2007/09/13/server-push-jpeg-stream/#comment-16512 Hi Adrian, I think it is the sequential execution of read and write that might be the contributor of the corruption of the incoming JPEG stream. Try to to parallel read and write using protected type. It may solve your problem. It is interesting enough to find someone who is working on the same area of interest. I am working on a client on Solaris but the server pushes streams of raw binary data of digital signals. I think the situation is almost similar here. 张薇 Hi Adrian,

I think it is the sequential execution of read and write that might be the contributor of the corruption of the incoming JPEG stream. Try to to parallel read and write using protected type. It may solve your problem.

It is interesting enough to find someone who is working on the same area of interest. I am working on a client on Solaris but the server pushes streams of raw binary data of digital signals. I think the situation is almost similar here.

张薇

]]>