Abstract of LAN chat application (using Java)

 

ABSTRACT

 

LAN chat application is one of easiest way to chat with a your friends through LAN. No internet connection is needed. The only thing which requires is server IP address and you will be able to connect to others members through LAN . It can help you to talk to your friends even you both do not have internet connection. As it is based on LAN. LAN i.e.  local area network which connect different client to each other and also client to main server. So we have used the same concept here we are connecting two client or client and server with each other and by providing the IP address we can talk with each other.

 

On the other hand file sharing application  is also implemented where a user can upload a file or download a file. We are providing the path to the directory where we have stored our file to the user who wants to download particular file.

 

 

INTRODUCTION

The growth of the Internet has led to new and faster forms of communication. There are now programs that allow users to communicate in real-time with one or more people. These instant messaging tools are commonly referred to as IRC (Internet Relay Chat). Some of these programs can be downloaded for free.

LAN chat is one the same way can be used to talk to your friend in your circle .All you have to do is to provide his IP address and then you both will get connect to each other and then you can talk.It is helpful because if you have any problem while solving something you do not have  to go to his room and to meet him and  you can talk to him on chat if you both are connected to each other and can get solution of your problem .Chat application is one of the most useful software which is used by every business to communicate with his employers if he is out of station.

File sharing  on the other hand is good tool to share those file which your friend wants from you or any other file which can be useful for other. The user can see this file after login to system and can download this file .It is one of the easiest way as it doesn’t require much knowledge for sharing and downloading.

OVEVIEW

The LAN  chat application which we have implemented contain following things :-

1.     LOGIN

2.     CHAT

3.     JOIN CHAT ROOM

4.     UPLOAD FILE

5.     DOWNLOAD FILE

LOGIN   :

 

 

·        In computer security, a login or logon is the process by which individual access to a computer system is controlled by identification of the user using credentials provided by the user.

·        A user can log in to a system to obtain access and can then log out or log  off (perform a logout / logoff) when the access is no longer needed.

·        To log out is to close off one's access to a computer system after having previously logged in.

·        The registered user  needs to provide his username and password to authenticate his account.

·        After successful  login user will allow to chat and upload and download file .

 

THERE ARE TWO MODULES IN IT:-

      1.ADMIN LOGIN

      2.USER LOGIN

 

ADMIN MODULE :-

1.Add new user :: Admin can add a new user.Whether to allow any one to create a account or not depends on user to this chat application .

 

2.View user :Admin has got the right to check the personal details of the user .He can see all user details .

 

3.Delete user :Admin can also delete user who is abusing  other member and who is not following the rules .

 

4.Update chatroom: Admin can update chat room  and can also limit a chat room a  fixed number if he finds that there is too much crowd in chat room .

 

5.Delete files:If admin finds that particular file is bad or containing  virus that he can delete that file.

 

 

USER MODULE

1.Profile update : User can update the information given by him such as name and about me .he can change it as many times as he want to there is no restriction in it.

 

2.Chat room : User can join any chat room he wish to join  and there is no restriction in it.

3.File upload : User can upload file from the client Machine to server machine.

4.File download User can download file from the server Machine to client machine.

 

 

CHAT

 

After logged in user is allowed to chat with each other in a group or in private. This help user to get any information or solution of their problem  and also to share his knowledge with others.

 

You can also connect with your friends only if you want to talk to him privately .

 

Same is in case of file sharing a user can download and upload file easily by just clicking the file .This is very easy process and any one can easily upload and download file.

 

JOIN CHAT ROOM

In this you can connect to particular room which is currently running or have at least 1 user in it .This type of room are made to share particular information. You can join any chat room if room is available and can talk to other people who are logged in right now .

 

UPLOAD FILE

This will help you to upload a particular file from your computer to a server which other can easily download.To upload a file a user must be logged in only then he can upload a file .A file should not be bad other wise admin has the right to delete it .

DOWNLOAD FILE

In this a user can download a particular file he wants to. For this a user just have to log in and then go to path where all files are available and then he has to click on that file and it will prompt a message to save a file to particular location and in this way you can download and save a file.

 

 

 

 

TECHNOLOGIES USED

 

Front end as: Eclipse helios

Back end as:  Mysql

Database:  Mysql

Querying language:   Sql

Forms: Jsp , Java servlet

External library  :  Apache common.fileupload , Apache.commons.io

 

REQUIREMENTS

 

System Requirements:

Operating System: Microsoft® Windows® XP/Vista/window7/linux

Processor: 1 Ghz

Memory: 512 MB RAM

Hard Disk Space: 45 MB Available HDD Space

Video Card: 3D graphics accelerator equivalent to GF6200 or higher

Sound Card: 16-bit Sound Card

DirectX® Version: DirectX® 9.0c

 

 

 

TABLES USED :

 

LOGIN

loginid VARCHAR2(30)	name VARCHAR2(30)	password VARCHAR2(30)	email VARCHAR2(30)	type VARCHAR2(30)

 

 

CHAT ROOMS:

 

roomname VARCHAR2(30)	roomdesc VARCHAR2(30)

 

 

 

 

 

SHARED FILES:

 

fileName VARCHAR2(30)	contenttype VARCHAR(30)	loginid VARCHAR2(30)

Read More

Introduction to Kafka & KsqlDB

 

An Introduction to Kafka

The amount of data in the world is growing exponentially and, according to the World Economic Forum, the number of bytes being stored in the world already far exceeds the number of stars in the observable universe. When you think of this data, you might think of piles of bytes sitting in data warehouses, in relational databases, or on distributed file systems. Systems like these have trained us to think of data in its resting state. In other words, data is sitting somewhere, resting, and when you need to process it, you run some query or job against the pile of bytes. This view of the world is the more traditional way of thinking about data. However, while data can certainly pile up in places, more often than not, it’s moving. You see, many systems generate continuous streams of data, including IoT sensors, medical sensors, financial systems, user and customer analytics software, application and server logs, and more. Even data that eventually finds a nice place to rest likely travels across the network at some point before it finds its forever home.

If we want to process data in real time, while it moves, we can’t simply wait for it to pile up somewhere and then run a query or job at some interval of our choosing. That approach can handle some business use cases, but many important use cases require us to process, enrich, transform, and respond to data incrementally as it becomes available. Therefore, we need something that has a very different worldview of data: a technology that gives us access to data in its flowing state, and which allows us to work with these continuous and unbounded data streams quickly and efficiently. This is where Apache Kafka comes in. Apache Kafka (or simply, Kafka) .

It is a streaming platform for ingesting, storing, accessing, and processing streams of data. While the entire platform is very interesting, this book focuses on what I find to be the most compelling part of Kafka: the stream processing layer. However, to understand Kafka Streams and ksqlDB (both of which operate at this layer, and the latter of which also operates at the stream ingestion layer), it is necessary to have a working knowledge of how Kafka, as a platform, works.

 An Introduction to KsqlDB

The story of ksqlDB is one of simplification and evolution. It was built with the same goal as Kafka Streams: simplify the process of building stream processing applications. However, as ksqlDB evolved, it became clear that its goals were much more ambitious than even Kafka Streams. That’s because it not only simplifies how we build stream processing applications, but also how we integrate these applications with other systems (including those external to Kafka). It does all of this with a SQL interface, making it easy for beginners and experts alike to leverage the power of Kafka.

Both Kafka Streams and ksqlDB are excellent tools to have in your stream processing toolbelt, and complement each other quite well. You can use ksqlDB for stream processing applications that can be expressed in SQL, and for easily setting up data sources and sinks to create end-to-end data processing pipelines using a single tool. On the other hand, you can use Kafka Streams for more complex applications, and your knowledge of that library will only deepen your understanding of ksqlDB since it’s actually built on top of Kafka Streams.

 

What Is ksqlDB?

ksqlDB is an open source event streaming database that was released by Confluent in 2017 (a little more than a year after Kafka Streams was introduced into the Kafka ecosystem). It simplifies the way stream processing applications are built, deployed, and maintained, by integrating two specialized components in the Kafka ecosystem (Kafka Connect and Kafka Streams) into a single system, and by giving us a high-level SQL interface for interacting with these components. Some of the things we can do with ksqlDB include:

Model data as either streams or tables (each of which is considered a collection in ksqlDB) using SQL.

Apply a wide number of SQL constructs (e.g., for joining, aggregating, transforming, filtering, and windowing data) to create new derived representations of data without touching a line of Java code.

Query streams and tables using push queries, which run continuously and emit/push results to clients whenever new data is available. Under the hood, push queries are compiled into Kafka Streams applications and are ideal for event-driven micro services that need to observe and react to events quickly.

When to Use ksqlDB

 It’s no surprise that higher-level abstractions are often easier to work with than their lower-level counterparts. However, if we were to just say, “SQL is easier to write than Java,” we’d be glossing over the many benefits of using ksqlDB that stem from its simpler interface and architecture. These benefits include:

More interactive workflows, thanks to a managed runtime that can compose and deconstruct stream processing applications on demand using an included CLI and REST service for submitting queries.

Less code to maintain since stream processing topologies are expressed using SQL instead of a JVM language.

Simplified architecture, since the interface for managing connectors (which integrate external data sources into Kafka) and transforming data are combined into a single system. There’s also an option for running Kafka Connect from the same JVM as ksqlDB.

Kafka Streams Integration

For the first two years of its life, ksqlDB was known as KSQL. Early development focused on its core feature: a streaming SQL engine that could parse and compile SQL statements into full-blown stream processing applications. In this early evolutionary form, KSQL was conceptually a mix between a traditional SQL database and Kafka Streams, borrowing features from relational databases (RDBMS) while using Kafka Streams to do the heavy lifting in the stream processing layer.

The most notable feature KSQL borrows from the RDBMS branch of the evolutionary tree is the SQL interface. This removed a language barrier for building stream processing applications in the Kafka ecosystem, since users were no longer required to use a JVM language like Java or Scala in order to use Kafka Streams.

 

 

Read More