User Tag List

Page 3 of 4 FirstFirst 1 2 3 4 LastLast
Results 21 to 30 of 32

Thread: MooClick protokol specifications

  1. #21
    Clicker Multimedia Fusion 2 DeveloperSWF Export Module

    Join Date
    Jun 2006
    Posts
    6,773
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    If you want to write a C++ implementation, it's pretty simple to wrap or inherit from the OBClient/OBServer classes in the OINC library.

  2. #22
    Clicker Fusion 2.5Fusion 2.5+ DLC

    Join Date
    Jun 2006
    Posts
    887
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    Hey, does anyone know how MooClick server detects disconnection? If there is some ping-pong mechanism for detecting alive connection..and if so, how about the message headers?

    I cant find good method on the server side to detects disconnection - on MSDN sending small packets is recommended - I would like to know how MooClick server does it in order to let my server work perfectly with MooClick client.

    The same is on the client side - how MooClick client recognizes disconnection from server? I think this would be very useful info.

    Thanks!

  3. #23
    Forum Moderator Fusion 2.5 DeveloperAndroid Export ModuleiOS Export ModuleSWF Export ModuleInstall Creator Pro
    Fusion 2.5 (Steam)Fusion 2.5 Developer (Steam)Fusion 2.5+ DLC (Steam)Android Export Module (Steam)HTML5 Export Module (Steam)iOS Export Module (Steam)Universal Windows Platform Export Module (Steam)

    Join Date
    Jun 2006
    Location
    England
    Posts
    3,515
    Mentioned
    3 Post(s)
    Tagged
    1 Thread(s)

    Re: MooClick protokol specifications

    Quote Originally Posted by Blizna
    Hey, does anyone know how MooClick server detects disconnection? If there is some ping-pong mechanism for detecting alive connection..and if so, how about the message headers?
    See http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=98490#Post98490
    .:::.Joshtek.:::.

  4. #24
    Clicker Fusion 2.5 DeveloperiOS Export ModuleInstall Creator Pro

    Join Date
    Jan 2007
    Posts
    62
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    Hi.

    Good to see someone has made use of my server. It has a couple of bugs, but still a good reference nonetheless.

    I have a protocol question myself:

    If string messages are preceded with 7, and integers preceded with 8, what are binaries preceded with?

    Once I have this information I can update my server to differentiate between the three message types.

    Cheers.

  5. #25
    Clicker Fusion 2.5 DeveloperiOS Export ModuleInstall Creator Pro

    Join Date
    Jan 2007
    Posts
    62
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    I found the answer: 9. I have another question: When the message starts with 8, is the integer encoded as four bytes or as a string representation?

  6. #26
    Clicker Multimedia Fusion 2SWF Export Module
    Jacob's Avatar
    Join Date
    Jul 2007
    Location
    Second pixel to the right
    Posts
    3,208
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    I think it's 4 bytes but I'm not positive...

  7. #27
    Clicker Fusion 2.5 DeveloperiOS Export ModuleInstall Creator Pro

    Join Date
    Jan 2007
    Posts
    62
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    I'm seeing four bytes, but someone was insisting it's a string. I'm sure I'll get to the bottom of it tomorrow.

  8. #28
    Clicker Multimedia Fusion 2 DeveloperSWF Export Module

    Join Date
    Jun 2006
    Posts
    6,773
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    It'll be four bytes.

  9. #29
    Clicker Fusion 2.5 DeveloperiOS Export ModuleInstall Creator Pro

    Join Date
    Jan 2007
    Posts
    62
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    I have another question:

    Most encoded commands use a single byte at the start to indicate the type of the command. However, when a connection sends its name to the server, in addition to a 12 byte is also sends a 3 byte and a 0 byte, then the name of the connection. The same happens when the server replies: it sends 12,3,0 followed by the connection ID. Does anyone know if there's any rational reason behind this? Is it possible that 12 could be followed by something else, in which case it's a command I don't know anything about?

  10. #30
    Forum Moderator Fusion 2.5 DeveloperAndroid Export ModuleSWF Export Module

    Join Date
    Jun 2006
    Location
    Merseyside, UK
    Posts
    398
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: MooClick protokol specifications

    I always wondered this too, I thought maybe it was for versioning so the client could tell the server what version of the API it supported and hence the server could be backwards compatible. But this is just a guess

Page 3 of 4 FirstFirst 1 2 3 4 LastLast

Similar Threads

  1. mooclick
    By nick_Peoples in forum The Games Factory 2 - Technical Support
    Replies: 19
    Last Post: 3rd January 2010, 04:45 PM
  2. i really need some help with mooclick
    By Dynamite in forum Multimedia Fusion 2 - Technical Support
    Replies: 13
    Last Post: 15th February 2007, 03:21 PM
  3. New MooClick bug appear (probably 242)
    By Blizna in forum Multimedia Fusion 2 - Technical Support
    Replies: 19
    Last Post: 1st December 2006, 06:11 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •