Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

Jump to content

Talk:Transaction-level modeling

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 12 years ago by 50.53.15.59 in topic "Bingo!"

"Bingo!"

[edit]
"Communication mechanisms such as busses or FIFOs are modeled as channels [...]"
  • Channels?
"Transaction requests take place by calling interface functions of these channel models [...]"
  • Transaction requests?

Thanks for any explanations. --Abdull (talk) 17:41, 29 January 2010 (UTC)Reply

TLM is basically two things put together and used as a single useful concept: event-driven simulation and choosing the right level of abstraction (what constitutes an event for what you want to simulate?). It is the idea to simulate what you need and not what you do not. In TLM nomenclature, a transaction request is an event (communication packet) that is queued/communicated via a channel. A channel an instance of a defined set of interfaces that connect processing blocks together. Think of them as parameters to an API where specific arguments can be assigned to these parameters during specific events/transactions. Basically it is a messaging system. 50.53.15.59 (talk) 10:38, 28 July 2013 (UTC)Reply