http://members.optushome.com.au/paulmotyer
Discussion in 3rd party please:
news://news.turbopower.com/turbopower.public.support.flashfiler.third-
party
The fixed issues are:
The server-side call: Transport.btGetConnectionID was returning
the ClientID of the wrong client and a 0 if the index supplied
was 0 (an off-by-one error)
SharedMem Transport worked fine with a Single Client-side
Connection but due to a bug in the Transport's ConnectionLost
processing it failed with multiple Client-Side connections
This is now fixed.
The Compression and Encryption code has been moved to their
own units and changed to components. This allows them to be
used by other Transports
If you use compression or encryption you'll need to change your
Client-Side components
But the user code needed is unchanged.
The documentation and example App have been changed to match
No D4 version is available yet
--
,-._|\ Paul Motyer [TPX]
/ Oz \ SoftStuff P/L
\_,--._/ [paul.motyer at tpx.turbopower dot com]
v [ http://members.optushome.com.au/paulmotyer ]
I've also tested Paul's transports (only on FF3) and they are indeed very
much faster (and more reliable) than the legacy transport.
> A new version of the new style, fast FF2.12 Transports have been
> released on my web site
Will your transports also work with FlashFiler 3???
Germain
> Will your transports also work with FlashFiler 3???
Yes. The same codebase compiles to D4 .. D7 and FF2 .. FF3. My testing
is 99% in FF3
--
Personal: [paulmotyer( at )optushome( dot )com( dot )au]