1
0
mirror of https://github.com/stefanocasazza/ULib.git synced 2025-09-28 19:05:55 +08:00
ULib/examples/simple_client_server
stefanocasazza 215c334a3f fix
2017-03-14 16:25:57 +01:00
..
client.cpp sync 2016-11-08 14:26:32 +01:00
Makefile.am bug fixing 2015-07-10 19:16:37 +02:00
Makefile.in fix 2017-03-14 16:25:57 +01:00
README some fix 2016-04-27 17:04:20 +02:00
server.cpp sync 2016-10-06 16:09:35 +02:00

This example (simple_client_server) is very old code and maybe now it can be source of confusion.
In general the need to subclass UClientImage<socket_type> or to make a plugin is very unusual.
I think that can be necessary in some unusual context, for example to manage a new protocol or some messaging system,
but in general the better way to generate dynamic response with ULib is to write a USP page.
There are many examples of USP pages in the directory: src/ulib/net/server/plugin/usp