Activity
From 06/23/2020 to 07/22/2020
07/22/2020
- 03:53 PM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- Greg Shah wrote:
> Any classes related to browse or other large data transfer usage will be high impact.
I unders... - 03:38 PM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- Any classes related to browse or other large data transfer usage will be high impact.
- 03:37 PM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- What is the next set of classes being worked?
07/21/2020
- 11:08 AM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- Greg Shah wrote:
> Code Review Task Branch 4011b Revision 11581
>
> The changes are good. Minor issues:
>
> 1... - 10:37 AM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- Code Review Task Branch 4011b Revision 11581
The changes are good. Minor issues:
1. @BrowseJasperDataSource@, ... - 08:37 AM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- Re-worked @ServerState@ and @ClientState@ (de)serialization.
A quick test was performed with Hotel GUI and a large ... - 04:07 AM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- Constantin Asofiei wrote:
> Some other notes:
> # @SyncMessage@ is mostly used by FWD, and not plain @Message@. Th... - 10:27 AM Feature #3789: rewrite writeObject and readObject to rely on NativeTypeSerializer or a similar ap...
- Constantin Asofiei wrote:
> Igor, how would @Message.payload@ be changed to use Kryo?
Constantin,
I've not anal... - 10:14 AM Feature #3789: rewrite writeObject and readObject to rely on NativeTypeSerializer or a similar ap...
- Igor, how would @Message.payload@ be changed to use Kryo?
- 10:06 AM Feature #3789: rewrite writeObject and readObject to rely on NativeTypeSerializer or a similar ap...
- A pure "hand-made" serialization (even with simple helper classes such as @NativeTypeSerializer@) has at least two di...
07/20/2020
- 07:50 PM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- Some other notes:
# @SyncMessage@ is mostly used by FWD, and not plain @Message@. This has an additional @Serializa... - 07:38 PM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- I am assuming that as a quick first pass you are going to implement @Externalizable@ in all of the classes passed ove...
07/19/2020
- 09:53 AM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- This is interesting. I think it is worth exploring.
We also have the ideas from #3789.
Some useful references:... - 09:47 AM Feature #4026: ensure all objects transmitted over the DAP implement Externalizable
- From Igor:
> Please note however that in many cases which I've seen, the implementation of the Externalizable in F...
Also available in: Atom