Simultaneous Odigo Messenger Sessions

Using a access database create a visual basic 6.0 application that retrieves the needed logon information such as the usernames and passwords from a table in the database which the application then uses to create a new instant of a Odigo messenger object. Each record in the database that contains the needed information becomes one of the Odigo messenger objects residing in memory. Each Odigo Messenger object should log on to the Odigo messenger service using the Odigo messenger ODIGO Protocol and be able to send and receive messages independent of each other Simultaneously. As proof of concept have each Odigo messenger object return a random record from a sample database as the reply to any received instant messages. Application must be fully documented and written in an object-oriented manner using class modules wherever possible and standard modules when not possible to use class modules. The idea behind this application is to have a single class module that is created and runs in memory each instance of this class should operate and function independently of the others. The object should utilize as much of the functionality available to the ODIGO Protocol as possible. The functionality of this application should be encapsulated into class modules easily added to my existing application. It is very important that functionality is self-contained in .bas and .cls files. No visual feedback is required to the user the objects in memory should run with no interaction from the user. These will mainly be standalone unattended database driven Odigo messenger bots. ## Deliverables Complete and fully functional working program(s) in executable form as well as complete source code of all work done. Complete copyrights to all work purchased. Application must demonstrate multiple instances of Odigo messenger object simultaneously running in memory communicating using ODIGO Protocol and operating independently of each other. Application must also be self contained in modules and be easily added to an existing project. Source code must be well documented. ## Deadline information Do not automate the Odigo Instant Message client, but instead use the Odigo protocol for all communication with the server. This includes sending and receiving instant messages to and from other users of the Odigo instant Messenger Service.