Package io.vertx.tp.jet.uca.tunnel

Class AbstractChannel

java.lang.Object
io.vertx.tp.jet.uca.tunnel.AbstractChannel
All Implemented Interfaces:
JtChannel
Direct Known Subclasses:
ActorChannel, AdaptorChannel, ConnectorChannel, DirectorChannel
public abstract class AbstractChannel extends Object implements JtChannel
Abstract channel reference matrix Name Database Integration Mission AdaptorChannel Yes No No ConnectorChannel Yes Yes No DirectorChannel Yes No Yes ActorChannel Yes Yes Yes

For above support list, here are some rules: 1) Request - Response MODE, Client send request 2) Publish - Subscribe MODE, Server send request

For common usage, it should use AdaptorChannel instead of other three types; If you want to send request to third part interface ( API ), you can use ConnectorChannel instead of others.

The left two: ActorChannel & DirectorChannel are Background task in zero ( Job Support ), the difference between them is that whether the channel support Integration.

The full feature of channel should be : ActorChannel

  • Constructor Details

    • AbstractChannel

      public AbstractChannel()

  • Method Details

    • transferAsync

      public io.vertx.core.Future<io.vertx.up.commune.Envelop> transferAsync(io.vertx.up.commune.Envelop envelop)
      Specified by:
      transferAsync in interface JtChannel

    • initAsync

      public abstract io.vertx.core.Future<Boolean> initAsync(JtComponent component, io.vertx.up.commune.ActIn request)

    • getLogger

      protected io.horizon.uca.log.Annal getLogger()

    • commercial

      protected io.horizon.specification.meta.action.Commercial commercial()

    • mission

      protected io.vertx.up.atom.worker.Mission mission()