MyTran Login

From Hotline Wiki
Revision as of 14:51, 3 January 2024 by Lostarch (talk | contribs) (Created page with " Constant: myTran_Login Initiator: Client Start login sequence with the server (see ''Transaction Sequences''). Fields used in the request: {| border="1" cellpadding="0" cellspacing="0" | style="width:.45in;"| '''ID''' | style="width:96px;"| '''Field Name''' | style="width:451px;"| ===Note=== |- | style="width:.45in;"| 105 | style="width:96px;"| User login | style="width:451px;"| |- | style="width:.45in;"| 106 | s...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


            Constant:               myTran_Login

Initiator: Client



Start login sequence with the server (see Transaction Sequences).



Fields used in the request:


ID

Field Name

Note[edit | edit source]

105

User login

106

User password

160

Version

Currently 151


Fields used in the reply:


ID[edit | edit source]

Field Name

Note[edit | edit source]

160

Version


If Version is >= 151, additional fields are included:


ID[edit | edit source]

Field Name

Note[edit | edit source]

161

Banner ID

Used for making HTTP request to get banner

162

Server name

Server name string


If server version is < 151, client sends Set Client User Info (304) transaction with only User Name (102) and User Icon ID (104) fields used, and does not expect a reply. It does not expect agreement to be received (109). Subsequently, it sends Get User Name List (300) request, followed by Get File Name List (200) or Get News Category Name List (370), depending on user preferences. After that, a banner is requested from HTTP server.