Difference between revisions of "Talk:Services"

From 3dbrew
Jump to navigation Jump to search
(Service notation suggestion)
 
m (→‎Service Command Notation: Forgot my signature)
 
Line 3: Line 3:
 
There seems to be some disagreement on how to notate commands on services. Some people do this: AMNet:OpenTicket (as done by the wiki for page naming), others do am:net::OpenTicket.
 
There seems to be some disagreement on how to notate commands on services. Some people do this: AMNet:OpenTicket (as done by the wiki for page naming), others do am:net::OpenTicket.
  
I'd like to propose that the wiki page naming continues with all-uppercase service names followed by initial uppercase port name (i.e., am:net -> AMNet, act:u -> ACTU, and so on), but that they are used in text to be more precise: am:net#OpenTicket, act:u#GetAccountDataBlock. This is loosely modeled after Ruby and Javadoc method notation.
+
I'd like to propose that the wiki page naming continues with all-uppercase service names followed by initial uppercase port name (i.e., am:net -> AMNet, act:u -> ACTU, and so on), but that they are used in text to be more precise: am:net#OpenTicket, act:u#GetAccountDataBlock. This is loosely modeled after Ruby and Javadoc method notation. [[User:Infinicore|Infinicore]] ([[User talk:Infinicore|talk]]) 09:15, 2 January 2016 (CET)

Latest revision as of 10:15, 2 January 2016

Service Command Notation[edit]

There seems to be some disagreement on how to notate commands on services. Some people do this: AMNet:OpenTicket (as done by the wiki for page naming), others do am:net::OpenTicket.

I'd like to propose that the wiki page naming continues with all-uppercase service names followed by initial uppercase port name (i.e., am:net -> AMNet, act:u -> ACTU, and so on), but that they are used in text to be more precise: am:net#OpenTicket, act:u#GetAccountDataBlock. This is loosely modeled after Ruby and Javadoc method notation. Infinicore (talk) 09:15, 2 January 2016 (CET)