[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-games-devel
Subject:    Re: [Kde-games-devel] kbattle.net
From:       Nikolas Zimmermann <wildfox () kde ! org>
Date:       2001-05-19 23:07:05
[Download RAW message or body]

On Sunday 20 May 2001 01:05, Rob Kaper wrote:
> On Sun, May 20, 2001 at 12:42:02AM +0200, Nikolas Zimmermann wrote:
> > Of course! No qt/kde for the _daemon_ no qdaemon :)
>
> Okay, count me in. :-)
>
> I guess we'll have to write down some sort of model and interaction scheme
> first though... what are the tasks of the server and what should be handled
> by the game itself?
>
everything's done by the client and the server
> - Chat/meeting place runs on server, clients display/enter data, I think we
>   agree on that..?
yes
> - Which of these do we want to support for actual games:
>   - a traditional KDE game client/server model, where kbattle.net takes
> care of most of the host/port stuff and tells the clients to start their
> server/client code
>   - a GGZ-alike model where game modules reside on the kbattle.net server
>     and clients only display/enter data
>   - a KMonop-alike model where games can require a dedicated server which
>     has nothing to do with kbattle.net, kbattle.net is only the
> meetingplace for finding players
right!
That's it a meetingplace
you can launch ie. kbattleship then and it only kbattle.net only takes
care of giving the one's ip to the other user ....
kbattle.net is "just" the lobby

>
> And of course, let's be cliche and:
>
> - register and host kbattle.net
who?
> - create a small, desperate homepage ;-)
yop, later
> - create a mailinglist (unless we want all the traffic at kde-games-devel,
>   do we? Or rather, does the rest of kde-games-devel?)
kde-games-devel!
>
> Rob

Bye
 Bye
  Niko

-- 
Nikolas Zimmermann
wildfox@kde.org
_______________________________________________
Kde-games-devel mailing list
Kde-games-devel@master.kde.org
http://master.kde.org/mailman/listinfo/kde-games-devel

[prev in list] [next in list] [prev in thread] [next in thread]