Jump to content

Search the Community

Showing results for tags 'multi-clients'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements and Site News
    • Administration
  • AutoIt v3
    • AutoIt Help and Support
    • AutoIt Technical Discussion
    • AutoIt Example Scripts
  • Scripting and Development
    • Developer General Discussion
    • Language Specific Discussion
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office

Categories

  • AutoIt Team
    • Beta
    • MVP
  • AutoIt
    • Automation
    • Databases and web connections
    • Data compression
    • Encryption and hash
    • Games
    • GUI Additions
    • Hardware
    • Information gathering
    • Internet protocol suite
    • Maths
    • Media
    • PDF
    • Security
    • Social Media and other Website API
    • Windows
  • Scripting and Development
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office

Categories

  • Forum FAQ
  • AutoIt

Calendars

  • Community Calendar

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Member Title


Location


WWW


Interests

Found 1 result

  1. Here I am again, with a brand new UDF! (not so new through...) Taking (great) advantage of the new maps feature, I made a simple, flexible multi-clients TCP server UDF. Features: You can create multiples servers in one scriptPeers limit is optional (the real peers limit is your RAM and the maps performances)You can configure max data receive len (2nd argument of TCPRecv) on a per-client basisYou can set an optional idle time-out (time without receiving any data before peer gets disconnected)Each peer has an empty Map that can contain user defined dataYou can set a function that will be called for each connected peer at pre-defined interval (onPeerCycle callback)The UDF is callback driven (onConnect, onDisconnect, onReceive, onError, onPeerCycle)You can set a disconnect message when kicking a peer. This message will be passed to the onDisconnect callbackonReceive callback must return the number of bytes that have been consumed. Say you receive 100 bytes of data but you used (consumed) only 70 bytes, by returning 70 from the callback the remaining 30 bytes will be buffered and passed again on the next call to onReceiveKnown bugs: TCPRecv bug! the function doesn't detect peer disconnection (hope this will be fixed soon)Download: https://github.com/matwachich/generic-tcp-server/ Thanks in advance for your feedback!
×
×
  • Create New...