When the MMS content is delivered, CP differentiates each service using the username and password parameters which also act as an authentication for the CP, therefore, each service must have a unique username. The authentication process is done on HTTP Header , with the following format :
POST /mm7adapter HTTP/1.0
Host: 192.168.31.143:9800
User-Agent: CDMS v.1.0
Authorization: Basic bG9hZHRlc3Q6bG9hZHRlc3Q=
Autorization header is following HTTP Basic authorization, as explained bellow:
Authorization: Basic base64_encode(“username:password”)
MM7 request messages shall be transferred in an HTTP POST request. MM7 responses shall be transferred in an HTTP Response message. The media type “text/xml” shall be used for messages containing only the SOAP envelope. MM7 requests that carry a SOAP attachment shall have a “multipart/related” Content-Type. The SOAP envelope shall be the first part of the MIME message and shall be indicated by the Start parameter of the multipart/related Content-Type. If a SOAP attachment is included it shall be encoded as a MIME part and shall be the second part of the HTTP Post message. The MIME part should have the appropriate content type(s) to identify the payload. Figures below provide few examples of the message structure. This MIME part shall have two MIME headers - Content-Type and Content-ID fields.
but what about the c2 reference? isn't that too being getting referenced to null when it is passed as the argument for the go method (to create the reference for c3)?
Cage<? extends Dog> cg1 = new Cage<Dog>();
In the first case, the type in LHS and RHS is the same. Why is it not the same in the second case? Why can't we write the following
Cage<? extends Dog> cg1 = new Cage<? extends Dog>();