[Freeciv-Dev] Re: Extended connect dialog (PR#977)

["Raimar Falke" <i-freeciv-lists@xxxxxxxxxxxxx>]

<URL: http://rt.freeciv.org/Ticket/Display.html?id=977 >

On Thu, Jan 22, 2004 at 10:25:18AM -0800, imbaczek@xxxxxxxxxxxxxx wrote:
> 
> <URL: http://rt.freeciv.org/Ticket/Display.html?id=977 >
> 
> On 04-01-22 you wrote:
> 
> > On Thu, Jan 22, 2004 at 04:28:33AM -0800, imbaczek@xxxxxxxxxxxxxx wrote:
> >>
> >> On 04-01-19 you wrote:
> >> 
> >> >> - Why do the packets you introduce require explicit (non-delta)
> >> >> handling?  Raimar?
> >> 
> >> > Technically there is no need to non-delta on any packet. It was added
> >> > for the first packets (connect req and the reply) to allow interaction
> >> > with old system. This is now obsolete since we renumbered the packets
> >> > anyway.
> >> 
> >> > So there is now a reason why the non-delta should stay in place (to
> >> > allow interaction with other delta systems) there is no need to add
> >> > more non-delta packets.
> >> 
> >> One good reason is traffic shaping,
> 
> > Please explain in more detail. What code shapes what traffic at what
> > level?
> 
> There are traffic shapers that analyze connections and adjust
> bandwidth depending on few first packets transmitted. Now if those
> packets are compressed, chances are they'll be very different among
> games -- something that a program can't know.
> 
> http://l7-filter.sourceforge.net/
> http://lartc.org/

Yes it is a reason but I doubt a good one. There are other ways to
identify freeciv traffic (by port number of example). Also these level
7 analyzers fail if you use encryption and maybe
compression. Nevertheless there is no issue since the first 2 packet
will stay non-delta and the compression will also stay always on. What
may be possible is that we sent a dummy uncompressed chunk of data
like "Freeciv client-server protocol" before the actual communication
starts.

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
  "With a PC, I always felt limited by the software available.
   On Unix, I am limited by my knowledge."
    -- Peter J. Schoenster <pschon@xxxxxxxxxxxxxxxxx>