11 | Reactor is a succinct and powerful foundational library for building reactive, FastData applications on the JVM. 12 | More detailed documentation is available on the reference guide. 14 |
15 |Can be applied to incoming and outgoing service interfaces.
27 | */
28 | @Retention(RetentionPolicy.RUNTIME)
29 | @Target(ElementType.METHOD)
30 | public @interface Ipc {
31 | String name() default "";
32 | }
--------------------------------------------------------------------------------
/src/docbook/xsl/html-singlepage.xsl:
--------------------------------------------------------------------------------
1 |
2 |
3 |
21 |
22 |
25 | *
26 | * @author Stephane Maldini
27 | * @since 0.6
28 | */
29 | @FunctionalInterface
30 | public interface Inbound
34 | * Clients or Receivers will onSubscribe when their connection is established. They
35 | * will complete when the unique returned closing {@link Publisher} completes itself or if
36 | * the connection is remotely terminated. Calling the returned {@link
37 | * Disposable#dispose()} from {@link Mono#subscribe()} will terminate the subscription
38 | * and underlying connection from the local peer.
39 | *
40 | * Servers or Producers will onSubscribe when their socket is bound locally. They will
41 | * never complete as many {@link Publisher} close selectors will be expected. Disposing
42 | * the returned {@link Mono} will safely call shutdown.
43 | *
44 | * @param
59 | * The IO handler will return {@link Publisher} to signal when to terminate the
60 | * underlying resource channel.
61 | *
62 | * @param ioHandler the in/out callback returning a closing publisher
63 | *
64 | * @return a {@link Mono} completing with a {@link Disposable} token to dispose
65 | * the active handler (server, client connection...) or failing with the connection
66 | * error.
67 | */
68 | Mono newHandler(BiFunction> ioHandler);
69 |
70 | }
71 |
--------------------------------------------------------------------------------
/src/docbook/xsl/xslthl/bourne-hl.xml:
--------------------------------------------------------------------------------
1 |
2 |
27 |
28 | * Writing and "flushing" is controlled by sinking 1 or more {@link #send(Publisher)} that
29 | * will forward data to outbound. When a drained Publisher completes or error, the channel
30 | * will automatically "flush" its pending writes.
31 | *
32 | * @author Stephane Maldini
33 | * @since 0.6
34 | */
35 | @FunctionalInterface
36 | public interface Outbound A new {@link Outbound} type (or the same) for typed send
52 | * sequences. An implementor can therefore specialize the Outbound after a first after
53 | * a prepending data publisher.
54 | *
55 | * @param dataStream the dataStream publishing OUT items to write on this channel
56 | *
57 | * @return A new {@link Outbound} to append further send. It will emit a complete
58 | * signal successful sequence write (e.g. after "flush") or any error during write.
59 | */
60 | Outbound'
32 | "
33 | '
36 | "
37 | Authors
130 |