mORMot Open Source

Why Use Fossil? There are plenty of open-source version control systems available on the internet these days. What makes Fossil worthy of attention? Bug Tracking And Wiki - In addition to doing distributed version control like Git and Mercurial, Fossil also supports

PK   a§#@~®Op´   
     whyusefossil3.txteŽ1nAE¯ò¸JŠ 
:ÐÖfÇa-Æ+ÛÚÛÇ+…*…ëý÷†iÅÕßê.õ€ËÄÆ ¼¥r‹ú]¸í\»Œ'›‹6ŒÚ´ÂW~8èIRéVÆĐlc{r¿Ðê{4³ÿñR‹TH
E$0·øêw\ŒÆYÚŸ-`Y°Ã©J'-„PÝò"&·\þÙU™G    PŽœÙÆnBõã
§ê
ïË'þPK    a§#@~®Op´   
                  whyusefossil3.txtPK      ?   ã     

  Ç Why Use Fossil? There aAwplenty o    f open-source version control sy  └stems available æ╞the internet !ΓQw  ┴days. What makesE
 wort±╢æFatt1Ʊÿ? B   Çug Tracking And Wiki - In addit±ÿ@   to do≥üdistributedlike Git aüfMe   rcurial,F
also supports 

  /// Fast low-level Socket implementation
  // - direct access to the OS (Windows, Linux) network layer
  // - use Open constructor to create a client to be connected to a server
  // - use Bind constructor to initialize a server
  // - use direct access to low level Windows or Linux network layer
  // - use SockIn and SockOut (after CreateSock*) to read or write data
  //  as with standard Delphi text files (see SendEmail implementation)
  // - if app is multi-threaded, use faster SockSend() instead of SockOut^
  //  for direct write access to the socket; but SockIn^ is much faster than
  // SockRecv() thanks to its internal buffer, even on multi-threaded app
  // (at least under Windows, it may be up to 10 times faster)
  // - but you can decide whatever to use none, one or both SockIn/SockOut
  // - our classes are much faster than the Indy or Synapse implementation
  TCrtSocket = class
  public
    /// initialized after Open() with socket
    Sock: TSocket;
   ...
   ...

{
About multithreading and event-driven:
    TWSocket is a pure asynchronous component. It is non-blocking and
    event-driven. It means that when you request an operation such as connect,
    the component start the operation your requested and give control back
    immediately while performing the operation in the background automatically.
    When the operation is done, an event is triggered (such as
    OnSessionConnected if you called Connect).

    This asynchronous non-blocking behaviour is very high performance but a
    little bit difficult to start with. For example, you can't call Connect and
    immediately call SendStr the line below. If you try, you'll have an
    exception triggered saying you are not connected. Calling connect will start
    connection process but will return long before connection is established.
    Calling SendStr at the next line will not work because the socket is not
    connected yet. To make it works the right way, you have to put your SendStr
    in the OnSessionConnected event.

    The asynchronous operation allows you to do several TCP/IP I/O
    simultaneously. Just use as many component as you need. Each one will
    operate independently of the other without blocking each other ! So you
    basically don't need multi-threading with TWSocket, unless YOUR processing
    is lengthy and blocking.

    If you have to use multithreading, you have two possibilities:
    1) Create your TWSocket from your thread's Execute method
    2) Attach a TWSocket to a given thread using ThreadAttach.
    In both cases, you must set MultiThreaded property to TRUE.
    If you don't use one of those methods, you'll end up with a false
    multithreaded program: all events will be processed by the main tread !
    For both methods to work, you MUST have a message loop withing your thread.
    Delphi create a message loop automatically for the main thread (it's in
    the Forms unit), but does NOT create one in a thread ! For your convenience,
    TWSocket has his own MessageLoop procedure. You can use it from your thread.

    Sample program MtSrv uses first method while ThrdSrv uses second method.
    Sample program TcpSrv is much the same as ThrdSrv but doesn't use any
    thread. You'll see that it is able to server a lot of simultaneous clients
    as well and it is much simpler.


 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *}
...

s3 := 0;
...
      inc(s1,P^[0]);
    inc(s3, P^[0]);
      inc(s2,s1);
      inc(s1,P^[1]);
    dec(s3,P^[1]);
      inc(s2,s1);
      inc(s1,P^[2]);
    inc(s3,P^[2]);
      inc(s2,s1);
      inc(s1,P^[3]);
    dec(s3,P^[3]);
      inc(s2,s1);
      inc(PtrUInt(P),16);