4bb89dcc54
Motivation: We did not correctly handle connect() and disconnect() in EpollDatagramChannel / KQueueDatagramChannel and so the behavior was different compared to NioDatagramChannel. Modifications: - Correct implement connect and disconnect methods - Share connect and related code - Add tests Result: EpollDatagramChannel / KQueueDatagramChannel also supports correctly connect() and disconnect() methods.
31 lines
1.1 KiB
Java
31 lines
1.1 KiB
Java
/*
|
|
* Copyright 2017 The Netty Project
|
|
*
|
|
* The Netty Project licenses this file to you under the Apache License,
|
|
* version 2.0 (the "License"); you may not use this file except in compliance
|
|
* with the License. You may obtain a copy of the License at:
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
* WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
* License for the specific language governing permissions and limitations
|
|
* under the License.
|
|
*/
|
|
package io.netty.channel.epoll;
|
|
|
|
import io.netty.bootstrap.Bootstrap;
|
|
import io.netty.testsuite.transport.TestsuitePermutation;
|
|
import io.netty.testsuite.transport.socket.DatagramConnectNotExistsTest;
|
|
|
|
import java.util.List;
|
|
|
|
public class EpollDatagramConnectNotExistsTest extends DatagramConnectNotExistsTest {
|
|
|
|
@Override
|
|
protected List<TestsuitePermutation.BootstrapFactory<Bootstrap>> newFactories() {
|
|
return EpollSocketTestPermutation.INSTANCE.datagramSocket();
|
|
}
|
|
}
|