Project

General

Profile

Actions

Feature #3444

closed

app-layer: signal stream engine about expected data size

Added by Victor Julien almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Description

Currently the TCP based app-layers assemble the buffer they work on themselves. This leads to unnecessary buffering and code complexity. Instead, the app-layer API should allow the parsers to signal to the stream layer below how much data they need before the record is complete.


Related issues

Related to Feature #3531: app-layer: signal stream engine about expected data size with next characterRejectedActions
Related to Optimization #3538: dns: use app-layer incomplete supportClosedJeff LucovskyActions
Related to Optimization #3539: rdp: use app-layer incomplete supportClosedZach KellyActions
Related to Optimization #3540: krb5: use app-layer incomplete supportNewPierre ChifflierActions
Related to Optimization #3541: applayertemplate: use app-layer incomplete supportClosedJason IshActions
Actions #1

Updated by Philippe Antoine over 1 year ago

And how much data can be released...

Actions #2

Updated by Victor Julien over 1 year ago

How do you mean released?

Actions #3

Updated by Victor Julien over 1 year ago

  • Status changed from Assigned to In Review
  • Target version changed from TBD to 6.0.0beta1
Actions #4

Updated by Victor Julien over 1 year ago

  • Status changed from In Review to Resolved
Actions #5

Updated by Victor Julien over 1 year ago

  • Related to Feature #3531: app-layer: signal stream engine about expected data size with next character added
Actions #6

Updated by Victor Julien over 1 year ago

  • Status changed from Resolved to Closed
Actions #7

Updated by Victor Julien over 1 year ago

Actions #8

Updated by Victor Julien over 1 year ago

Actions #9

Updated by Victor Julien over 1 year ago

Actions #10

Updated by Victor Julien over 1 year ago

Actions

Also available in: Atom PDF