Two problems; First, the maximum size of a text variable isn't 32000 bytes anymore, which leads me to believe this was an oversight and not a feature... :)
Second, it was easy to receive text until a stop character is received, as long as the data is less than 32K. When your packets become larger than 32K it becomes more complicated. In my use case it was easy since we'll only ever receive one 'packet' per connection, but the code grows more complicated if you need to support an arbitrary number. What's the problem with removing the arbitrary 32K limit? > On Apr 10, 2020, at 9:09 AM, Rob Laveaux via 4D_Tech <[email protected]> > wrote: > > The data that is available from the stream can be any arbitrary size. The > plugin does not know upfront how many bytes are available, so it needs a > limit. There is a default value, which you can override if it doesn’t suit > you. > > So please tell me, what is the problem? ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
