Examples of de.uniluebeck.itm.ncoap.communication.dispatching.client.TokenFactory

de.uniluebeck.itm.ncoap.communication.dispatching.client.TokenFactory

The TokenFactory generates tokens to match inbound responses with open requests and enable the {@link de.uniluebeck.itm.ncoap.communication.dispatching.client.ClientCallbackManager} to invoke the correct callback method.The CoAP specification makes no assumptions how to interpret the bytes returned by {@link Token#getBytes()()}, i.e. a {@link Token} instances where {@link Token#getBytes()} returns an empty byte array is different from a{@link Token} where {@link Token#getBytes()} returns a byte array containing one "zero byte" (all bits set to 0).Furthermore, both of these {@link Token}s differ from another {@link Token} that is backed by a byte arraycontaining two "zero bytes" and so on... This leads to 257 ((2^8) + 1) different tokens for a maximum token length of 1 or 65793 different tokens ((2^16) + (2^8) + 1) for a maximum token length of 2 and so on and so forth... @author Oliver Kleine

        });


        this.exeutor = new ScheduledThreadPoolExecutor(threads, threadFactory);
        this.exeutor.setRemoveOnCancelPolicy(true);


        TokenFactory tokenFactory = new TokenFactory(maxTokenLength);


        //Create factories for channel and pipeline
        ChannelFactory channelFactory = new NioDatagramChannelFactory(exeutor, threads/2);
        ClientChannelPipelineFactory clientChannelPipelineFactory =
                new ClientChannelPipelineFactory(exeutor, tokenFactory);

Examples of de.uniluebeck.itm.ncoap.communication.dispatching.client.TokenFactory

Related Classes of de.uniluebeck.itm.ncoap.communication.dispatching.client.TokenFactory