Package org.gnome.soup

Interface ServerCallback

All Superinterfaces:

FunctionPointer

Functional Interface:

This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.

@FunctionalInterface
@Generated("io.github.jwharm.JavaGI")
public interface ServerCallback
extends FunctionPointer

Functional interface declaration of the ServerCallback callback.

See Also:

• run(org.gnome.soup.Server, org.gnome.soup.ServerMessage, java.lang.String, org.gnome.glib.HashTable<java.lang.String, java.lang.String>)

Method Summary

Modifier and Type	Method	Description
void	run(Server server, ServerMessage msg, String path, @Nullable HashTable<String,String> query)	A callback used to handle requests to a Server.
default MemorySegment	toCallback(Arena arena)	Creates a native function pointer to the upcall(java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment) method.
default void	upcall(MemorySegment server, MemorySegment msg, MemorySegment path, MemorySegment query, MemorySegment userData)	The upcall method is called from native code.

Method Details

run

void run(Server server,
 ServerMessage msg,
 String path,
 @Nullable HashTable<String,String> query)

A callback used to handle requests to a Server.

path and query contain the likewise-named components of the Request-URI, subject to certain assumptions. By default, Server decodes all percent-encoding in the URI path, such that "/foo%2Fbar" is treated the same as "/foo/bar". If your server is serving resources in some non-POSIX-filesystem namespace, you may want to distinguish those as two distinct paths. In that case, you can set the Server:raw-paths property when creating the Server, and it will leave those characters undecoded.

query contains the query component of the Request-URI parsed according to the rules for HTML form handling. Although this is the only commonly-used query string format in HTTP, there is nothing that actually requires that HTTP URIs use that format; if your server needs to use some other format, you can just ignore query, and call Message.getUri() and parse the URI's query field yourself.

See Server.addHandler(java.lang.String, org.gnome.soup.ServerCallback) and Server.addEarlyHandler(java.lang.String, org.gnome.soup.ServerCallback) for details of what handlers can/should do.

upcall

default void upcall(MemorySegment server,
 MemorySegment msg,
 MemorySegment path,
 MemorySegment query,
 MemorySegment userData)

The upcall method is called from native code. The parameters are marshaled and run(org.gnome.soup.Server, org.gnome.soup.ServerMessage, java.lang.String, org.gnome.glib.HashTable<java.lang.String, java.lang.String>) is executed.

toCallback

default MemorySegment toCallback(Arena arena)

Creates a native function pointer to the upcall(java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment, java.lang.foreign.MemorySegment) method.

Specified by:

toCallback in interface FunctionPointer

Parameters:

arena - the arena in which the function pointer is allocated

Returns:

the native function pointer