Result for 2A5815D1680269F812322CC182B00827B3B5994F

Query result

Key Value
FileName./usr/include/Eris-1.2/Eris/Metaserver.h
FileSize5089
MD51B30A8E79DDDE7CD0696607B78856748
SHA-12A5815D1680269F812322CC182B00827B3B5994F
SHA-2566CB28D44FF6E620E4CC645D0CF5211C6607B9AB837F767168F2F02B896077637
SSDEEP96:cVvuLRmPyv3pEFVOJmTBK044XK2ilezjb4s/U+8h1dAu4:cVsay/pEFVomTt40K2BXkB+6XAB
TLSHT15DB1A803A52C6BB7D59200AFC02CF193B3BE8595B3C395515EFBC02F4A52095D3669D3
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize57608
MD5525263CE60D21D47A6717FF2552851FC
PackageDescriptionThe WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2-dev
PackageSectionlibdevel
PackageVersion1.1.1.0-3
SHA-138F75526F6CC1BF376A080F754A95CC60EDCAFEA
SHA-2561385E07AA39D49FA929901386B8EDEE48AE77D5AD328281C41D25A1EBC841D28
Key Value
FileSize57614
MD5A29A26BF8A4651092E2F6CDA40A3625E
PackageDescriptionThe WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2-dev
PackageSectionlibdevel
PackageVersion1.1.1.0-3
SHA-1D2539F6FCCFEA427CC3C817351A95B1C3B4B1734
SHA-256C25BE6B8A5B1721B2CB4F5A7BE0E52FAD12F3351A0F5F2E4B5D4FB3A673499FE
Key Value
FileSize57620
MD5B66846FC9E9E58C75D40DCC96FA7F5A5
PackageDescriptionThe WorldForge client entity library - development files Eris is designed to simplify client development (and avoid repeating the same work several times), by providing a common system to deal with the back end tasks. Notably, Eris encapsulates most of the work in getting Atlas entities available on your client, logging into a server, and managing updates from the server. Thus it can be considered as a session layer above Atlas, providing persistent (for the session) objects as opposed to Atlas ones (which are transient). It handles the client-side implementation of the meta-server protocol, and querying game servers; out-of-game (OOG) operations (via the Lobby and Rooms), and most important in-game (IG) operations such as entity creation, movement and updates. . Eris provides a generic 'Entity' class, which you are free to sub-class and provide to the system (by registering a factory with the World); thus you are free to create different classes to handle characters, walls, vehicles, etc as your client dictates. An alternative approach is to simply create peer classes, and connect them to Eris via callbacks. Eris makes extensive use of libSigC++, which must be correctly installed and functioning on your system. Familiarity with signal/slot programming concepts is essential for using Eris; the libSigC++ home-page has some examples. Gtk+ or QT signal systems also provide a good introduction. . This package contains the development files for compiling software depending on Eris.
PackageMaintainerMichael Koch <konqueror@gmx.de>
PackageNameliberis-1.2-dev
PackageSectionlibdevel
PackageVersion1.1.1.0-3
SHA-1963F13C6E626B6A17BAD0F8221372AB22E3B9946
SHA-25675BF529395A15EE1F9716FB39D27BF9FF4F533A57BB9CA55547C35626411888E