
BUGS, limitations or points to ponder :)

Bug-levels: A == Concerns everybody, * == Code geeks only

[A] - Using smodem to download ("D") on some area and entering
      a <file??.ext> pattern with upload redirection enabled
	  causes the user to be moved to the upload area before
	  the files are selected?

[*] - When background checker dies, something happens with dsockfd,
      so that select() reports that there is something to be
      read from the socket. Normally we only expect 
      "struct VMatik_nodemessage" from the socket, and if the socket
      is not set to O_NONBLOCK, the read() function hangs
      because there is not enough bytes to read.
      
      Find out: What is sent to the socket and why? How to know
      how many bytes are waiting to be read from the socket,
      and if the waiting data is what we want or something else?
      
      Current workaround: socket is set to O_NONBLOCK, and when
      doing read() the resulting amount of bytes is checked to
      match with sizeof(struct VMatik_nodemessage).

[A] - The FTP pseudo protocol is disabled (besides, I have never
      tested it)

[A] - Users can not currently describe their uploads. BGChecker
      is the reason for this. Following behaviours could be had:
      1) Ask descs after bgchecker has finished. But what if
         user logoffs before that?
      2) Ask descs after upload is finished (could only affect
         those that bgchecker has already processed, or then
         another process would need to go through the log)

[A] - There is no file- or filearea editor yet. You'll have to
      use SQL for that at the moment.


