Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "AIMProviderForECF"

(→‎Abstract)
(→‎Detailed Description)
Line 9: Line 9:
  
 
===Detailed Description===
 
===Detailed Description===
−
"Client" here would refer to the contestants and students .
+
JOscar is an easy-to-use, robust library for connecting to AOL Instant Messenger from Java. This project will use JOscar to implement the AIM Provider for ECF. The main concerns is as follows:
−
"Server" here would refer to the person hosting the Judge .
+
* AIM namespace and implement the AIM IDs.
−
 
+
* the ContainerInstantiator for AIM Provider.
−
* First of all the communication will be totally centralized on jabber servers. The basic idea is pretty simple: The person hosting the judge will add the clients to his/her list. The code submitted by the client will be run on the judge's machine. (The interface will be definitely attractive and easy to use).
+
* the AIMContainer and AIMPresenceContainer, AIMChatRootManager
−
* Stress will be laid on the Interface so that people can submit codes while chatting with the group at the same time. This would certainly increase interaction and enthusiasm.
+
* the FileTransfer for AIM Provider(org.eclipse.ecf.filetransfer)
−
* Group chat can be easily accomplished by existing API of ECF. Hence not much of time will be required to accomplish this task.
+
* the Shared Object for AIM Provider.
−
* Working on the Judge Engine will be the major part. The code retrieved will be compiled and executed first. Multiple languages will be supported.
+
* the Datashare for AIM Provider.
−
* To start of with: C, C++ and Java codes can be submitted. To compile C/C++ codes: GCC(for Linux) or MinGW(for Windows) will be required. Java compilation will require JVM to be installed in the server machine.
+
* some GUI for AIM Provider. Which is important for AIM Provider
−
* The server will also have an option to log all the information for every code submissions. This would enable the users to check their history of submissions and details. A rank list will be maintained in case if its a programming contest. MYSQL can be used (connected via JDBC) to accomplish this task.  
+
−
* Emails will be sent to each client automatically after each code submission. The Email would include the source code, the result, Errors if any, Time of Execution, Memory taken etc.
+
−
* File download feature will also be added to help the clients during a programming session/match.
+
  
 
===Experience in this Field===
 
===Experience in this Field===

Revision as of 13:39, 29 March 2009

Project Description:

Title

AIM Provider for ECF

Abstract

ECF allows messaging protocols to be plugged in as providers. ECF has supports a lot of messaging protocols, gtalk, msn, yahoo and so on. But AIM isn't currently supported. First this project choose to wrap an existing Java library (JOscar), because It is quick to finish in this way. It is possible to implement the AIM protocol in this project.

Detailed Description

JOscar is an easy-to-use, robust library for connecting to AOL Instant Messenger from Java. This project will use JOscar to implement the AIM Provider for ECF. The main concerns is as follows:

  • AIM namespace and implement the AIM IDs.
  • the ContainerInstantiator for AIM Provider.
  • the AIMContainer and AIMPresenceContainer, AIMChatRootManager
  • the FileTransfer for AIM Provider(org.eclipse.ecf.filetransfer)
  • the Shared Object for AIM Provider.
  • the Datashare for AIM Provider.
  • some GUI for AIM Provider. Which is important for AIM Provider

Experience in this Field

Retrieved from "https://wiki.eclipse.org/index.php?title=AIMProviderForECF&oldid=146808"

Back to the top