![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I think I know the answer to this but I want to ask it anyway. I have database application where I store images into. I use update chunk to store the image into the database. My chunk definition defines three 64k pieces and I'm using indirect chunking. I should be able to send the entire image in one call shouldn't I? Instead I get a 3022. If I send it one 64k chunk at a time it works. But what's the use of indirect chunking if I can't define multiple 64k chunks in the chunk descriptor? The docs say that the requirement is that the chunk descriptor must fit in the data buffer? Which is does... So why can't I do this? It almost seems like there is a parameter that I can tweak to make this work but I can't find it. Someone explain this to me. |
#3
| |||
| |||
|
|
The 64K limit applies to the Btrieve call, and this includes the chunk data, not just the descriptor, even in an indirect chunk. Using an indirect chunk makes your application faster by eliminating the need to transfer the chunk data from your application memory into a separate data buffer for the Btrieve call. It is just there to make your program faster -- and not a way around the limit. Goldstar Software Inc. Building on Btrieve(R) for the Future(SM) Bill Bach BillBach (AT) goldstarsoftware (DOT) com http://www.goldstarsoftware.com *** Pervasive.SQL Service & Support Classes *** Chicago: March, 2004: See our web site for details! |
#4
| |||
| |||
|
|
Thanks... that's what I thought... so there is no way to adjust the packet size? "Bill Bach" <bbach (AT) cncdsl (DOT) com> wrote in message news:4032B118.95801A85 (AT) cncdsl (DOT) com... The 64K limit applies to the Btrieve call, and this includes the chunk data, not just the descriptor, even in an indirect chunk. Using an indirect chunk makes your application faster by eliminating the need to transfer the chunk data from your application memory into a separate data buffer for the Btrieve call. It is just there to make your program faster -- and not a way around the limit. Goldstar Software Inc. Building on Btrieve(R) for the Future(SM) Bill Bach BillBach (AT) goldstarsoftware (DOT) com http://www.goldstarsoftware.com *** Pervasive.SQL Service & Support Classes *** Chicago: March, 2004: See our web site for details! |
#5
| |||
| |||
|
|
It is not actually the network packet size. It is the data buffer. It has been defined as 64K in size forever. The data buffer length specifier is 16 bits so that is as big as it can get. Leonard On Wed, 18 Feb 2004 15:18:22 GMT, "Wendell Buckner" wendellbuckner (AT) sbcglobal (DOT) net> wrote: Thanks... that's what I thought... so there is no way to adjust the packet size? "Bill Bach" <bbach (AT) cncdsl (DOT) com> wrote in message news:4032B118.95801A85 (AT) cncdsl (DOT) com... The 64K limit applies to the Btrieve call, and this includes the chunk data, not just the descriptor, even in an indirect chunk. Using an indirect chunk makes your application faster by eliminating the need to transfer the chunk data from your application memory into a separate data buffer for the Btrieve call. It is just there to make your program faster -- and not a way around the limit. Goldstar Software Inc. Building on Btrieve(R) for the Future(SM) Bill Bach BillBach (AT) goldstarsoftware (DOT) com http://www.goldstarsoftware.com *** Pervasive.SQL Service & Support Classes *** Chicago: March, 2004: See our web site for details! |
![]() |
| Thread Tools | |
| Display Modes | |
| |