2 @page application Describing your application
8 - *Actor* (or process in legacy interfaces of SimGrid)
10 - *Activities*: resource usage that applications do. This is what
13 Any given actor can do at most one foreground activity, while it
14 can also do several non-blocking activities in the background.
16 - These activities take place on *Resources* (links, compute
17 machine, disks). Resources should be described (created) in the
18 Virtual Platform (link), but your application have many other ways
19 to interact with the resource.
21 - The resources are arranged in a hierarchy of *Networking Zones*,
22 with which the application can also interact. The netzone knows the
23 networking path between one resource to another.
25 Speak of mailboxes here? Where if not?
27 * Interfaces to describe applications
29 - Simple C++ interface: S4U that is currently designed
30 - Simple Legacy C interfaces: MSG and SimDag, with comparison.
31 - Simple Java Interface: Currently MSG-based, but will be replaced with S4U stuff when ready
33 - Event-oriented, and trace-based. The old documentation of the
34 obsolete MSG module was removed in
35 https://github.com/simgrid/simgrid/commit/e05361c201fb95d2b7605e59001cd0a49a489739
37 - Arbitrary applications: Simterpose and Remote SimGrid (they are currently far from being usable).
38 - State our goal of BYOS (build your own simulator), even if it's just a neat name for now