1 Reply Latest reply on Jan 4, 2008 7:09 AM by SriScape

    Issue with Message Channels for RemoteObjects

    SriScape
      Hi

      I am reposting this message in this forum (already posted in "Flex2 General Discussion" by mistake)

      I have defined two message channels in my services-config.xml. One for over ssl (https) and one for regular http.

      <channels>
      <channel-definition id="my-graniteamf" class="mx.messaging.channels.AMFChannel">
      <endpoint
      uri=" http://{server.name}:{server.port}/{context.root}/graniteamf/amf"
      class="flex.messaging.endpoints.AMFEndpoint"/>
      </channel-definition>
      <channel-definition id="my-secure-graniteamf" class="mx.messaging.channels.SecureAMFChannel">
      <endpoint
      uri="https://{server.name}:{server.port}/{context.root}/graniteamf/amf"
      class="flex.messaging.endpoints.SecureAMFEndpoint"/>
      </channel-definition>
      </channels>

      I am referring to these in the services using default-channels as below...

      <default-channels>
      <channel ref="my-secure-graniteamf"/>
      <channel ref="my-graniteamf"/>
      </default-channels>.

      When i am accessing the application using http, first the secure endpoint is being pinged (obviously fails) and then the regular endpoint is being pinged and that works.

      When i am accessing the application using https, first the regular endpoint is being pinged (fails) and then the secure endpoint is being pinged and works.

      My question is why the order of look up is different, according to the documentation the order of lookup is the order mentioned in the services-config.xml.

      Another issue i have is that, when access the app using Fire Fox, it tries to ping the secure endpoint forever when accessing the app over http and tries to ping the non-secure endpoint when accessing the app over https server.

      I am using GraniteDS and flex beta 3.

      -Sri
        • 1. Re: Issue with Message Channels for RemoteObjects
          SriScape Level 1
          quote:

          Originally posted by: SriScape
          Hi

          I am reposting this message in this forum (already posted in "Flex2 General Discussion" by mistake)

          I have defined two message channels in my services-config.xml. One for over ssl (https) and one for regular http.

          <channels>
          <channel-definition id="my-graniteamf" class="mx.messaging.channels.AMFChannel">
          <endpoint
          uri=" http://{server.name}:{server.port}/{context.root}/graniteamf/amf"
          class="flex.messaging.endpoints.AMFEndpoint"/>
          </channel-definition>
          <channel-definition id="my-secure-graniteamf" class="mx.messaging.channels.SecureAMFChannel">
          <endpoint
          uri="https://{server.name}:{server.port}/{context.root}/graniteamf/amf"
          class="flex.messaging.endpoints.SecureAMFEndpoint"/>
          </channel-definition>
          </channels>

          I am referring to these in the services using default-channels as below...

          <default-channels>
          <channel ref="my-secure-graniteamf"/>
          <channel ref="my-graniteamf"/>
          </default-channels>.

          When i am accessing the application using http, first the secure endpoint is being pinged (obviously fails) and then the regular endpoint is being pinged and that works.

          When i am accessing the application using https, first the regular endpoint is being pinged (fails) and then the secure endpoint is being pinged and works.

          My question is why the order of look up is different, according to the documentation the order of lookup is the order mentioned in the services-config.xml.

          Another issue i have is that, when access the app using Fire Fox, it tries to ping the secure endpoint forever when accessing the app over http and tries to ping the non-secure endpoint when accessing the app over https server.

          I am using GraniteDS and flex beta 3.

          -Sri