lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Hi Paco,

The chapter about networking will include LuaSocket module which is a
part of Copas.
I'd love to include SQLlite3 in this book, but I'm limited with the
total amount of pages. After all, I've been using Lua binding for
SQLlite3 database engine by myself over last 2 years.
Right now it looks like the book will be over 300 pages. :)
So to ensure the quality of content I had to exclude few things like
graphical post-processing effects, sound effects, threads...
I may as well write another book later if there will be a demand.

With regards,


Dňa 7.3.2014 10:55 Paco Willers  wrote / napísal(a):
> Hi Mario,
> That sounds interesting to me. In my spare time as a hobby I'm
> developing an online text-based game using Lua. It's far from finished,
> but I hope some day I will be able to release it.
> I am using Lua to a certain skill, and I think I know enough about Lua
> to be able to review your book, but I assume you are coming across
> better candidates.
> I am looking forward to your book. Here are some personal hints at
> subjects I am (humbly and partly) experienced in, you may include these
> subjects in the book.
> Creating online text-based games... It's retro (I like that) and it is
> very easy to do using the Copas module. Of course things could be made
> more complex by handling the Telnet protocol and terminal control
> characters. One could also (read: "one is obliged to") add security
> measures like blocking clients that fail to login several times. Perhaps
> you know a way of using an encrypted network connection. I don't, so I
> will post a question in this mailing list in a few moments.
> I think Lua + Copas is also an easy and appropriate framework to create
> a backend to graphical online games, even for mobile games that run on
> Android or iOS, because the backend only has to handle text commands
> received by the graphical client, apply the game rules, and then return
> the result to the graphical frontend. In that case, parsing the commands
> is easy and needs little error handling: the graphical client doesn't
> make typos and only uses the commands you designed it to... unless
> someone uses a terminal emulator and hacks his/her way into your
> backend. :-)
> I also recommend writing a chapter about saving game states/data, by
> serializing tables or using SQLite3 to store your data into a database
> file. I personally like SQLite3. It's easy to incorporate it into a Lua
> application.
> Have a nice day,
> -- 
> Paco Willers < <>>