On Thu, Apr 16, 2015 at 5:01 PM, Feng Xiao wrote:
>
> Lazy does not affect the wire format. It doesn't even affect the generated
> API. What happens should be that, when the Java side receives the data from
> the C++ side, it will store lazy fields in a LazyField class where the data
> is stored i
On Thu, Apr 16, 2015 at 4:55 PM, Gianluca Borello
wrote:
> On Thu, Apr 16, 2015 at 2:08 PM, Feng Xiao wrote:
> >
> > It's either already working for Java, or only requires small tweaks for
> it
> > to work. Could you check if marking a field lazy makes any difference in
> > Java? If not please h
On Thu, Apr 16, 2015 at 2:08 PM, Feng Xiao wrote:
>
> It's either already working for Java, or only requires small tweaks for it
> to work. Could you check if marking a field lazy makes any difference in
> Java? If not please help file an issue on our github site.
>
Thanks for your reply, Feng.
On Wed, Apr 15, 2015 at 9:56 PM, Gianluca Borello
wrote:
> Hello,
>
> At my current company we're heavy protobuf users, but we started
> facing a big limitation: in the current Java implementation, since
> there's no lazy parsing, or ability to do direct sub-message parsing,
> we pay a huge penal