franta-hg@1: franta-hg@1: franta-hg@0: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@11: franta-hg@27: franta-hg@10: franta-hg@5: franta-hg@5: franta-hg@12: franta-hg@10: franta-hg@10: franta-hg@10: franta-hg@10: franta-hg@37: franta-hg@5: franta-hg@5: franta-hg@0: franta-hg@15: franta-hg@28: franta-hg@28: a provider which does not have own wireless network infrastructure; but does marketing and sets the prices for subscribers franta-hg@0: franta-hg@0: franta-hg@41: franta-hg@41: a company that provides technical services to MVNO thus MVNO can focus on marketing, pricing, brand and customer care franta-hg@41: franta-hg@41: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@28: franta-hg@28: franta-hg@33: a technique used in charging; franta-hg@28: for pre-paid subscribers the standard way to charge services is online franta-hg@30: – subscriber's balance is checked in the billing system and if sufficient, the service (e.g. sending a SMS) is provided, otherwise the service is denied; franta-hg@30: if the billing system is not currently available (so we can't say if the subscriber's balance is high enough), we can provide the service anyway and try to charge it later; franta-hg@30: this feature requires saving state (transactions which weren't charged yet) in some persitent storage (CDR files, SQL database etc.) franta-hg@30: and can be done at the billing gateway or directly at system like SMSC franta-hg@28: franta-hg@28: franta-hg@30: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@26: franta-hg@26: franta-hg@26: a service or particular short text message sent from or to a mobile phone; franta-hg@26: length of the content in one message is 140 bytes (octets), the number of characters depends on encoding, if 7-bit one is used, it is well known 160 characters; franta-hg@26: the number „160“ is iconic for SMS franta-hg@26: franta-hg@26: franta-hg@27: messaging franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: a unit of digital information; franta-hg@26: byte (almost always) consists of 8 bits, which means 256 possible values (2^8); franta-hg@26: octet is a synonym for 8-bit byte which accents that we really mean the 8-bit byte (and not e.g. the 7-bit one) franta-hg@26: franta-hg@26: franta-hg@27: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@30: franta-hg@30: franta-hg@30: specific kind of MOAT short message which is used to donate money to charity or some organization; franta-hg@30: the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS franta-hg@30: franta-hg@30: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@12: computer franta-hg@12: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@28: an XML-based file format for vector graphics franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@33: franta-hg@33: franta-hg@33: franta-hg@33: a kind of electronic communication between two persons or a group chat; franta-hg@33: compared to e-mail, IM messages are short (few words, sentence) and the other side is expected (depending on his/her online status) to read and respond it immediately; franta-hg@33: compared to SMS, IM messages are cheap – typically free of charge; franta-hg@33: important IM feature is presence – the sender knows current status of the recipient: online, offline, away, busy etc.; franta-hg@50: IM is rooted in the computer world but nowadays it is often used also on mobile phones as an alternative to (expensive) SMS – in such case it is called OTT and requires mobile Internet connectivity; franta-hg@33: IM messages are usually transferred over an TCP/IP protocol – good example is Jabber/XMPP which is free and open protocol for IM and presence based on XML franta-hg@33: franta-hg@33: franta-hg@9: computer franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@38: franta-hg@38: franta-hg@38: messaging franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: messaging franta-hg@38: franta-hg@38: franta-hg@34: franta-hg@50: franta-hg@50: franta-hg@50: franta-hg@50: a communication protocol for messaging based on XML; franta-hg@50: used for transferring franta-hg@50: IM messages, franta-hg@50: presence information (statuses like: online, busy, away etc.), franta-hg@50: contact list (called roster here) management, franta-hg@50: singaling of VoIP and video, file transfers etc.; franta-hg@50: can be also used as generic messaging protocol for connecting computer systems (not only human-human interaction) franta-hg@50: or for human-computer interaction (for accessing services like dictionaries, weather forecast or TV guide) franta-hg@50: franta-hg@50: franta-hg@34: computer franta-hg@34: xml franta-hg@34: messaging franta-hg@37: protocol franta-hg@34: franta-hg@34: franta-hg@50: franta-hg@50: a contact list; term used by Jabber/XMPP franta-hg@50: franta-hg@50: computer franta-hg@50: messaging franta-hg@50: franta-hg@50: franta-hg@12: franta-hg@12: franta-hg@28: franta-hg@28: franta-hg@28: a text-based client-server protocol for accessing e-mail mailbox; franta-hg@28: supports franta-hg@28: multiple hierarchical folders (inbox, sent, drafts… or user defined), franta-hg@28: marging messages with tags/flags, franta-hg@28: notifications of new messages from server to client (the client does not have to periodically check the inbox and just waits for new messages), franta-hg@28: full-text search and other features; franta-hg@28: messages usually stays at server storage after reading which allows using multiple client programs/devices; franta-hg@28: is more complex than POP3 protocol; franta-hg@28: uses TCP and standard port is 143 (STARTTLS or unencrypted) or 993 (SSL/TLS) franta-hg@28: franta-hg@28: franta-hg@9: computer franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@28: franta-hg@28: franta-hg@28: a text-based client-server protocol for accessing e-mail mailbox; franta-hg@28: messages are usually deleted from server after reading and are stored only on the client side; franta-hg@28: nowadays the more advanced IMAP4 protocol is often used instead of POP3; franta-hg@28: uses TCP and standard port is 110 (STARTTLS or unencrypted) or 995 (SSL/TLS) franta-hg@28: franta-hg@28: franta-hg@9: computer franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@42: franta-hg@28: franta-hg@28: franta-hg@28: a text-based client-server protocol for sending e-mail messages franta-hg@43: uses TCP and standard port is 25 (STARTTLS or unencrypted) or 465 (SSL/TLS) or 587 (STARTTLS or unencrypted for Message Submission – RFC 6409); franta-hg@43: is defined in RFC 5321 franta-hg@28: franta-hg@28: franta-hg@9: computer franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@42: franta-hg@42: franta-hg@42: franta-hg@42: a derivative of ESMTP designed for transferring messages locally from MTA component to MDA (mail storage, no queue); franta-hg@42: uses TCP/IP but must not use port 25 (SMTP); franta-hg@42: is defined in RFC 2033 franta-hg@42: franta-hg@42: franta-hg@42: computer franta-hg@42: messaging franta-hg@42: protocol franta-hg@42: franta-hg@42: franta-hg@12: franta-hg@40: franta-hg@40: franta-hg@40: an e-mail client – a software used for managing user's e-mail; franta-hg@40: because the MUA (like most client software) runs only when user needs it, franta-hg@40: the messages from the Internet are received by a remote MTA over the SMTP protocol, franta-hg@40: then delivered using an MDA into user's remote mailbox, franta-hg@40: from which they are obtained by the MUA using POP3 or IMAP4 protocols; franta-hg@40: when sending an e-mail, the MUA composes the message in RFC 5322 format and then submits it using the SMTP protocol to a MTA or MSA server; franta-hg@40: examples of MUA: Mozilla Thunderbird, KMail, Evolution, Mutt, Lotus Notes franta-hg@40: franta-hg@40: franta-hg@12: computer franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@49: franta-hg@49: franta-hg@42: franta-hg@42: franta-hg@42: franta-hg@44: a software component which transferres e-mails from one computer to another using SMTP protocol (implements both sending and receiving); franta-hg@44: messages can be passed over network (relayed) or for local recipients stored locally (passing them to the MDA using LMTP); franta-hg@44: examples of MTA: Postfix, Sendmail, Exim, Courier Mail Server, Apache James franta-hg@42: franta-hg@42: franta-hg@9: computer franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@49: franta-hg@45: franta-hg@45: franta-hg@45: a software component dedicated to receive e-mails from MUA; franta-hg@45: cooperates with MTA or is often integrated in MTA as one of its features; franta-hg@45: uses a variant of SMTP (RFC 6409) and TCP port 587 (different than SMTP/MTA port 25) franta-hg@45: franta-hg@45: franta-hg@40: computer franta-hg@40: messaging franta-hg@40: franta-hg@40: franta-hg@49: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: a software component that receives e-mail from the MTA and stores them in the recipient's mailbox; franta-hg@46: the MDA can also apply Sieve filters on processed messages; franta-hg@46: examples of MDA: Dovecot, Cyrus IMAP, procmail, maildrop franta-hg@46: franta-hg@46: franta-hg@46: computer franta-hg@46: messaging franta-hg@46: franta-hg@46: franta-hg@49: franta-hg@48: franta-hg@48: franta-hg@48: a software component that fetches e-mails from remote server (over POP3 or IMAP4 protocol) franta-hg@48: and then passes them to the MDA for local storage, or over SMTP to an MTA, or directly delivers it to the mailbox, or prints to standard output etc.; franta-hg@48: implements pull (not push) approach: fetches messages periodically (or on user's demand) franta-hg@48: instead of waiting for incoming messages and receiving them immediatelly when they emerge (like MTA does); franta-hg@48: examples of MRA: fetchmail, getmail franta-hg@48: franta-hg@48: franta-hg@48: computer franta-hg@48: messaging franta-hg@48: franta-hg@48: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: a standardized language for describing e-mail filters; franta-hg@46: the MDA can apply system-wide or user-defined filters on incoming messages; franta-hg@47: a filter has conditions (connected by logical operators: AND, OR…) like „message header contains value X“ franta-hg@47: and actions that will be done with the message like „file into folder X“ or „add flag/label X“ or „redirect message to some.address@example.com“ or „discard message“; franta-hg@46: filters are executed on the server where MDA resides, franta-hg@47: so they are independent of the MUA currently used by the user franta-hg@46: and works even if the user is offline (useful for OOTO messages when the user is on vacation) franta-hg@46: franta-hg@46: franta-hg@46: computer franta-hg@46: messaging franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@48: an automatic response on a message (e-mail, SMS etc.) which is sent when the recipient is for example on vacation and can't respond immediately; franta-hg@46: in case of e-mail it can be easily configured as a Sieve filter franta-hg@46: franta-hg@46: franta-hg@12: computer franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: acision franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@11: charging franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@11: charging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@16: franta-hg@16: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@19: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: finance franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: security franta-hg@10: charging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@6: ericsson franta-hg@10: charging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: nsn franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@35: franta-hg@35: franta-hg@35: franta-hg@35: the party (sender or recipient) who is charged for the service (e.g. SMS); franta-hg@35: MOMT messages (or other traffic) are typically charged to the sender (A); franta-hg@35: AOMT messages (like weather forecast or news) are typically charged to the recipient (B); franta-hg@35: some messages can be free of charge and some can be charged to both party (AB) franta-hg@35: franta-hg@35: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@36: franta-hg@36: franta-hg@38: a subscriber of a mobile network, a customer of a telco operator franta-hg@38: (but term „customer“ is ambiguous because „customer“ from SW development team point of view is the telco operator) franta-hg@36: franta-hg@36: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@24: franta-hg@24: franta-hg@24: charging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: charging franta-hg@24: franta-hg@24: franta-hg@12: franta-hg@12: franta-hg@24: franta-hg@24: franta-hg@24: kind of log file in machine-readable format (ASN.1, XML, CSV etc.) franta-hg@24: which describes particular usages of a service – e.g. placed phone call, sent SMS, Internet connection; franta-hg@24: CDR/SDR files are used for post-paid billing (not processed online but in batch) and as documentation of usage; franta-hg@24: they must be handled carefully because they contain private information (who calls or texts who); franta-hg@24: always respect subscriber's privacy! franta-hg@24: franta-hg@24: franta-hg@24: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@24: traffic which comes from a cell phone resp. mobile network, e.g. an SMS sent from your Handy franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@24: traffic which comes to a cell phone resp. mobile network, e.g. a received SMS franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@24: traffic which comes from an application i.e. not from the mobile network/phone, e.g. some weather forecast messages generated by an SPA franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@24: traffic which comes to an application i.e. not to the mobile network/phone, e.g. message sent to an application in order to subscribe the service or to send your vote franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: e.g. when Bob texts Alice from his phone to her phone franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: e.g. if Bob subscribes a weather forecast service by sending a message from his phone franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: e.g. if Alice receives to her phone a news message which she has previously subscribed franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@28: if two applications communicates over an SMS gateway and there are no cell phones involved; this is pretty rare, but somewhere you can meet such configuration franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: a cell phone franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: security franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@10: franta-hg@10: franta-hg@27: messaging franta-hg@10: franta-hg@10: franta-hg@12: franta-hg@36: franta-hg@36: franta-hg@36: a provider who operates an ESME (application) franta-hg@36: franta-hg@36: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@36: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@36: franta-hg@36: franta-hg@36: an application a software component which sends and receives messages (SMS, MMS, e-mail…) and is connected over IP (not directly attached to mobile network) and protocol like SMPP; franta-hg@36: often is operated by different company than telco operator – a VASP; franta-hg@36: franta-hg@36: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@6: franta-hg@6: franta-hg@6: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: Nokia's protocol for sending and receiving MMS, is based on HTTP and transferres binary content. franta-hg@12: nsn franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: an extension of UCP franta-hg@12: acision franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: nsn franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: A simple protocol that can be used between AAG and SPA for transmitting messages. Uses HTTP GET method and encodes data in the URL or in HTTP response body franta-hg@12: acision franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@10: franta-hg@27: messaging franta-hg@10: franta-hg@10: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@12: an implementation of SMSC from Acision franta-hg@6: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@38: roaming of subscribers from other operator in your network franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@38: roaming of your subscribers in other operator's network franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@39: franta-hg@39: franta-hg@39: (0x00) Unknown type of number; franta-hg@39: (0x01) International number; franta-hg@39: (0x02) National number; franta-hg@39: (0x03) Network specific number; franta-hg@39: (0x04) Subscriber number, dedicated access, short code; franta-hg@39: (0x05) Alphanumeric, in 7-bit GSM alphabet; franta-hg@39: (0x06) Abbreviated number franta-hg@39: franta-hg@39: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@39: franta-hg@39: franta-hg@39: a number which indicates the numbering plan of a telephone number; franta-hg@39: values: franta-hg@39: (0x00) Unknown numbering plan; franta-hg@39: (0x01) ISDN/telephone numbering plan – E.164/E.163; franta-hg@39: (0x02) Generic; franta-hg@39: (0x03) Data numbering plan – X.121; franta-hg@39: (0x04) Telex numbering plan – F.96; franta-hg@39: (0x05) Service Centre Specific plan; franta-hg@39: (0x06) Land mobile numbering plan – E.212; franta-hg@39: (0x07) ISDN/mobile numbering plan – E.214; franta-hg@39: franta-hg@39: (0x08) National numbering plan; franta-hg@39: (0x09) Private numbering plan; franta-hg@39: (0x0A) ERMES numbering plan – ETSI DE/PS 3 01-3; franta-hg@39: (0x0D) Binary Internet addres – IP; franta-hg@39: (0x0E) Alphanumeric Internet address franta-hg@39: franta-hg@39: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: acision franta-hg@27: messaging franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@19: franta-hg@19: franta-hg@19: computer franta-hg@19: xml franta-hg@19: franta-hg@19: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@19: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: computer franta-hg@12: java franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@19: franta-hg@19: Documentation of Java source code (classes, enumerations, interfaces, packages). Describes API and software's internals. Is useful for developers, not too much for end-users. franta-hg@19: computer franta-hg@19: java franta-hg@19: franta-hg@19: franta-hg@0: franta-hg@4: franta-hg@9: ericsson franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@28: franta-hg@28: franta-hg@28: computer franta-hg@28: franta-hg@28: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: java franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: xml franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@11: franta-hg@37: security franta-hg@37: protocol franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: security franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@53: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@15: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@51: franta-hg@52: franta-hg@52: franta-hg@51: a Java technology for monitoring and managing applications or devices; franta-hg@51: similar to SNMP; franta-hg@51: managed objects (MBeans) can emit events, can be asked for values (e.g. counters) or an action (method) can be called on them; franta-hg@51: this native Java technology can be also adapted/translated to other protocols like SNMP or WS/SOAP and integrated with the non-Java world; franta-hg@51: thanks to this abstraction, the managed object can implement only simple Java interface and don't have to deal with other protocols (which is job of generic adaptors) franta-hg@52: franta-hg@52: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@51: franta-hg@52: franta-hg@53: a Java API for message-oriented middleware (MOM); franta-hg@52: allows JEE components to create, send, receive and read messages; franta-hg@52: supports both point-to-point and publish-subscribe messaging models; franta-hg@53: can be adapted/translated to many other protocols like SMTP, AMQP, XMPP or SOAP; franta-hg@52: is defined in JSR 914; franta-hg@52: examples of JMS implementations: Apache ActiveMQ, OpenJMS, HornetQ franta-hg@52: franta-hg@51: franta-hg@9: computer franta-hg@10: java franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@52: franta-hg@52: franta-hg@52: franta-hg@52: a software (or even hardware) infrastructure for sending and receiving messages; franta-hg@52: can also offer routing and transformation features; franta-hg@52: for Java the MOM API is standardized as JMS franta-hg@52: franta-hg@52: franta-hg@52: computer franta-hg@52: messaging franta-hg@52: franta-hg@52: franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: an open and standard binary protocol for message-oriented middleware (MOM); franta-hg@53: is vendor and platform independent; franta-hg@53: whereas JMS defines programming API and is Java specific, the AMQP defines the wire-level protocol; franta-hg@53: so JMS (or other language/platform specific API) can be used inside the system and AMQP can be used for interconnection of systems in heterogenous environment; franta-hg@53: example of implementation: Apache ActiveMQ franta-hg@53: franta-hg@53: franta-hg@53: computer franta-hg@53: messaging franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: the format of data sent over the network as stream of bytes; franta-hg@53: an application layer protocol franta-hg@53: franta-hg@53: franta-hg@53: computer franta-hg@53: franta-hg@53: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@52: franta-hg@52: franta-hg@52: computer franta-hg@52: java franta-hg@52: franta-hg@52: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: a request for changing a software – new features or modification of existing ones; franta-hg@30: when one or more CRs are developed, they are delivered as new version of software product; franta-hg@30: CR is requested by the customer (mobile network operator) and is delivered by the development team; franta-hg@30: CR consists of one or more DT which are assigned to particular developers franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: a task assigned to a software developer; franta-hg@30: one or more DTs together usually forms a CR; franta-hg@30: it is also possible to have an internal DT which is not linked to any CR (e.g. some refactoring or fixes or maintenence which was not requested by the customer); franta-hg@30: each commit in the versioning system should be linked to a DT franta-hg@30: franta-hg@30: franta-hg@30: computer franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: a request for fixing something in the production; franta-hg@30: requires some investigation and then can be solved by changing the configuration on site or by fixing the software (development) franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: requirements on a software product or its particular change; franta-hg@30: is written from the system's point of view franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: requirements on a software product or its particular change; franta-hg@30: is written from the user's point of view franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@11: franta-hg@30: franta-hg@30: franta-hg@30: a build of a software product which was not done according to regular procedure and processes; franta-hg@30: might be used only for testing on site or during development – not in production; franta-hg@30: such software is often delivered as a tar.gz or JAR, WAR etc. file to be patched into existing installation, not as regular package (RPM, DEB etc.) as production version franta-hg@30: franta-hg@30: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@24: franta-hg@24: franta-hg@24: computer franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: computer franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: computer franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: computer franta-hg@24: franta-hg@24: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: general franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: acision franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@7: franta-hg@22: franta-hg@22: delivering better product faster with smaller teams of less-experienced engineers franta-hg@22: franta-hg@22: franta-hg@22: franta-hg@22: franta-hg@22: an company which is not going to bankrupt franta-hg@22: franta-hg@22: franta-hg@22: franta-hg@12: franta-hg@11: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: franta-hg@11: Something that should or will be done later. Used as comments in draft version of documents or in software source code. franta-hg@11: franta-hg@11: franta-hg@7: franta-hg@7: and so forth, and the rest franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: for instance, for example franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: in other words, that is franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: among other things franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: note well, note franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: percent, for each one hundred franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: annually franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: approximately franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: a document summarizing your relevant job experience and education franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: and others, and co-workers franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: after what has been written; used at the end of the letters/messages for additions franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: which was to be demonstrated franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: rest in peace franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: against franta-hg@8: general franta-hg@7: franta-hg@0: