Talk:PAT.Message Handling

From OIAr Archive 2013
Jump to navigation Jump to search

Building Block Type Removal

  • Suggestion: Remove Data Scanning, since this is one specific way to inspect data in the act of Filtering. Message Filtering itself can be used to provide the source of the modelling of different implementation variants of filtering, like Message Filtering.Header checking or Message Filtering.Content checking. In other words: or you name both at the Type level, or you name none. --Daniel Jumelet 11:49, 7 November 2011 (CET)
Message Filtering is a message-specific version of Traffic Filtering; that function only checks traffic characteristics, not content. With messages, the division between characteristics and content is more blurry, but not absent. For both Traffic Filtering and Message Filtering I use the test case of virus scanning. Viruses travel in the payload, and require content inspection - hence Data Scanning. An analogy for this is the police checking traffic on the A2 highway:
  • traffic filtering is like checking vehicles without stopping them: checks on license plates, speed, vehicle axle weight, et cetera, but NOT on the content of each vehicle.
  • Data scanning is the roadblock that checks the passengers, drivers' licence, cargo, cargo papers et cetera.
I see a big conceptual difference between the two, and would like to see two different BBTs to reflect this, both in WA Network and WA Middleware. However, I believe Data Scanning can safely be reused, hence Traffic Filtering & Data Scanning, and Message Filtering & Data Scanning. --Jan Schoonderbeek 09:58, 11 November 2011 (CET)
  • Suggestion: Remove Header Modification, since this is a specific form of Message Transformation. Other specific manipulations of messages are: 'message splitting', 'message aggregation', 'message resequencing', 'message enrichment' and 'message content translation' --Rinus van der Kolk 12:18, 7 November 2011 (CET)