Hoto yana aiki a kan haɗin kai tsaye mai sauri, amma ba ya cika ta hanyar forward proxy mai hankali. Wata hanyar da za ta iya haifar da hakan ita ce asalin yana rufe haɗin yayin da ake rubuta amsarsa.

Netty I/O asynchronous ne. Komawa daga writeAndFlush ba ya nufin an kammala wannan aiki. Don haka wannan tsari ba shi da aminci ga amsar da ke da bytes a cikin layi:

ctx.writeAndFlush(response);
ctx.close();

Lokacin da ake rufe musayar HTTP da gangan bayan saƙon amsarsa na ƙarshe, haɗa rufewar da future na wannan rubutun:

ctx.writeAndFlush(finalResponseMessage)
    .addListener(ChannelFutureListener.CLOSE);

Sashin yana ɗauka cewa an riga an gina amsar kuma an tsara ta daidai. Ga jiki da ake watsawa, yi amfani da kammalawar saƙonsa na ƙarshe maimakon rubuta kawunanso. Ga haɗin HTTP mai dorewa, kar a ƙara rufewa kawai saboda amsa ta ƙare.

Bincika gazawar future a matsayin ɓangare na yadda aikace-aikacen ke magance kuskure. Kammalawa ta ƙunshi gazawa da sokewa, don haka kammalawa ita kaɗai ba ita ce shaidar isar da ita daga browser ba.

Kwatanci mai amfani shi ne cikakken tsayin amsa da sakamakon rubutu a kowace hanya. Proxy na iya canza lokaci isa ya bayyana kuskuren rayuwa da ke akwai; kasancewarsa ba ya tabbatar da cewa compressor ko cache ɗinsa ya jefar da bytes.

Labarai masu alaƙa