From: brett l. <wak...@gm...> - 2008-08-07 22:26:17
|
On Thu, Aug 7, 2008 at 2:01 PM, John A. Tamplin <jat...@ja...> wrote: > On Thu, 7 Aug 2008, Erik Vos wrote: > >> That sounds like an interesting option. How is client-server communication >> organized in this concept? > > It looks like normal Java RPC, except that the RPC is async (ie, you get > callbacks when it returns). > >> A problem we would have with plain HTTP is, that the server will send >> unsolicited messages (i.e. updates from moves by other players). > > This can be done with Comet or hanging gets. > > One other benefit I didn't menion is that you can debug the client code in > Eclipse (or other IDE) as easily as your server code. > The down side, of course, is that we'd need to rewrite all of the GUI code. The GUI code isn't great, but it's currently functioning enough to be usable. Unless John is volunteering to do the porting, I don't really see where this suggestion moves the project forward. Tossing out our currently functioning GUI code and redoing the same thing over again rather than working on either adding new features or improving existing capability just doesn't seem very productive to me. > -- > John A. Tamplin ja...@ja... > 770/436-5387 HOME 4116 Manson Ave > Smyrna, GA 30082-3723 > ---Brett. |