Actualy Socket, UDP and VMpipe TransportType are defined staticly in TransportType.java, why not move that to each Transport implementation ? So serial comm transport can be added as regular Datagram or Socket transport (and VM Pipe or UDP being removed easly of the code for a personalized low size compilation :) )
Juilen Le mercredi 17 janvier 2007 à 23:28 -0800, Trustin Lee (JIRA) a écrit : > [ > https://issues.apache.org/jira/browse/DIRMINA-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Trustin Lee resolved DIRMINA-16. > -------------------------------- > > Resolution: Fixed > Fix Version/s: 2.0 > > Fixed again. This time, it's much more flexible than before. TransportType > is an interface now, so you can do whatever you want as long as you don't > break the contract. > > > org.apache.mina.common.TransportType > > ------------------------------------ > > > > Key: DIRMINA-16 > > URL: https://issues.apache.org/jira/browse/DIRMINA-16 > > Project: MINA > > Issue Type: Improvement > > Environment: Improve TransportType for permit to extend MINA > > supported transport types > > Reporter: Julien Vermillard > > Assigned To: Trustin Lee > > Fix For: 2.0, 0.7 > > > > > > the TransportType define the differents TransportType in MINA > > (Socket,Datagram, VM Pipe). The types are static and hardcoded. The > > constructor of Transport type is private. It leave no room for new > > Transport. > > I propose : > > 1st : change the transportType constructor visibility to public > > 2snd : move the staticly defined TransportTypes to the different > > io.datagram, io.socket, etc.. packages >
