6,264
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + Line 16:
Line 18: + + + +
no edit summary
Nintendo provides application developers with an API, which behind the scenes communicate with certain services. Services in this sense are system processes running in the background which wait for incoming requests. When a process wants to communicate with a service, it first needs to get a handle to the named service, and then it can communicate with the service via interprocess communication. Each service has a name up to 8 characters, for example "nim:u".
Nintendo provides application developers with an API, which behind the scenes communicate with certain services. Services in this sense are system processes running in the background which wait for incoming requests. When a process wants to communicate with a service, it first needs to get a handle to the named service, and then it can communicate with the service via interprocess communication. Each service has a name up to 8 characters, for example "nim:u".
Handles for services are retrieved from the service manager port, "srv:". Services are an abstraction of ports, they operate the same way except regular ports can have their handles retrieved directly from a SVC.
List of services:
List of services:
* [[Development Services PXI]]
* [[Development Services PXI]]
* [[Gamecard Services PXI]]
* [[Gamecard Services PXI]]
List of ports:
* [[Process Manager Ports]]
* [[ErrDisp]]