Instant messaging

[Peter O'Reilly]

<chris@yahoo.com> wrote in message
news:#Txy19sUDHA.3312@tk2msftngp13.phx.gbl...

> Has anyone built a web-based instant messaging system - or bought one?

Yahoo, AOL, MSN...free...it's hard to beat. ;-)
--
Peter O'Reilly

i think you missed the point

WEB-based

also, not a public network - something that can be used to allow 2 people on
the same web-site to communicate with each other - like chat, but one-on-one



"Peter O'Reilly" <Peter_OReilly@timeinc.com!N!O!.S!P!AM!> wrote in message
news:eEkzhGtUDHA.2204@TK2MSFTNGP12.phx.gbl...

> <chris@yahoo.com> wrote in message
> news:#Txy19sUDHA.3312@tk2msftngp13.phx.gbl...

> > Has anyone built a web-based instant messaging system - or bought one?

> Yahoo, AOL, MSN...free...it's hard to beat. ;-)
> --
> Peter O'Reilly
>
>

[Ryan Gregg]

I know there is a nice library written in Java to allow you to connect to
AIM through TOC. I've loaded it up in J# and compiled it with just a few
modifications. You could call that from inside ASP.NET and make your own
interface that way. The Jaim library is what I'm thinking of,
[url]http://jaimlib.sourceforge.net/[/url].

It'd take some work, but it's definitely possible.

Ryan


<chris@yahoo.com> wrote in message
news:%23Txy19sUDHA.3312@tk2msftngp13.phx.gbl...

> Has anyone built a web-based instant messaging system - or bought one?
> Looking for anyone who has implemented/purchased one already for
> advice/pointers/ any suggestions?
>
>
> Cheers
>
> Chris
>
>

[Peter O'Reilly]

<chris@yahoo.com> wrote in message
news:eVadHZtUDHA.392@TK2MSFTNGP11.phx.gbl...

> i think you missed the point
>

I don't think so. Not in the least.

> WEB-based
>
> also, not a public network

You mean like a private world wide WEB :-) The ones I cited use the HTTP
protocol; in that respect they are "web" based. I presume that is what you
mean.

>>>- something that can be used to allow 2 people on

> the same web-site to communicate with each other - like chat, but

one-on-one

Since *private* (not originally specified in your 1st message), one could
have fun building a UI wrapper to the Windows "net send " command statement
and do so on the cheap, too or use Microsoft chat one of those hidden, long
last forgotten utilities nobody seems to use. Ok, its not WEB -
nevermind.

How private things are (which you did not allude to in your 1st message) is
a matter of network setup, i.e. parameters that exist outside of ASP.NET.

Regarding ASP.NET and the .NET framework, you can use HTTP or TCP protocols
to communicate. Like AOL, MSN, and Yahoo, you will need to develop a small
memory resident desktop "listener" application or windows service. This
listener application is also where the user types and sends chat messages.
With this listener application you would incorporate .NET web services to
communicate with other participants sending SOAP formatted HTTP
requests/responses. The .NET web services framework takes care of the
SOAPing seemlessly for you.

Another ASP.NET specific server application logic would need to be written
to relay the message sent from person A to person B and vice versa. This
app would also tell your listener app who is logged in, etc.

That's how it would be done in .NET.

Good luck!

--
Peter O'Reilly

[Michal A. Valasek]

Hello,

| Has anyone built a web-based instant messaging system - or bought one?
| Looking for anyone who has implemented/purchased one already for
| advice/pointers/ any suggestions?

today I think the best solution would be use MSN messenger, resp. Exchange
messaging. Of course, it's possible to write that application on your own. I
wrote one application, years ago, before the .NET. But I'm afraid that it
would be unusable for you, because is completely in Czech language.

If you want solution accessed by web browser, it's really simple. If you
want real instant messaging, then I recommend to create one backend server,
which would communicate via web service interface with clients (winforms).
Complexivity of that application may vary, basic solution is one-night-work.

--
Michal A. Valasek, Altair Communications, [url]http://www.altaircom.net[/url]
Please do not reply to this e-mail, for contact see [url]http://www.rider.cz[/url]

[Alvin Bruney]

msn chat exposes itself as a .net com object from the tools menu. play with
it see what you come up with.
<chris@yahoo.com> wrote in message
news:#Txy19sUDHA.3312@tk2msftngp13.phx.gbl...

> Has anyone built a web-based instant messaging system - or bought one?
> Looking for anyone who has implemented/purchased one already for
> advice/pointers/ any suggestions?
>
>
> Cheers
>
> Chris
>
>

lol,

nah, i didn't mean the communication should be web-based, i meant the client
should be web-based!!!!!



"Peter O'Reilly" <Peter_OReilly@timeinc.com!N!O!.S!P!AM!> wrote in message
news:uwDe8AvUDHA.1152@tk2msftngp13.phx.gbl...

> <chris@yahoo.com> wrote in message
> news:eVadHZtUDHA.392@TK2MSFTNGP11.phx.gbl...

> > i think you missed the point
> >

> I don't think so. Not in the least.
>

> > WEB-based
> >
> > also, not a public network

>
> You mean like a private world wide WEB :-) The ones I cited use the HTTP
> protocol; in that respect they are "web" based. I presume that is what

you

> mean.
>

> >>>- something that can be used to allow 2 people on

> > the same web-site to communicate with each other - like chat, but

> one-on-one
>
> Since *private* (not originally specified in your 1st message), one could
> have fun building a UI wrapper to the Windows "net send " command

statement

> and do so on the cheap, too or use Microsoft chat one of those hidden,

long

> last forgotten utilities nobody seems to use. Ok, its not WEB -
> nevermind.
>
> How private things are (which you did not allude to in your 1st message)

is

> a matter of network setup, i.e. parameters that exist outside of ASP.NET.
>
> Regarding ASP.NET and the .NET framework, you can use HTTP or TCP

protocols

> to communicate. Like AOL, MSN, and Yahoo, you will need to develop a

small

> memory resident desktop "listener" application or windows service. This
> listener application is also where the user types and sends chat messages.
> With this listener application you would incorporate .NET web services to
> communicate with other participants sending SOAP formatted HTTP
> requests/responses. The .NET web services framework takes care of the
> SOAPing seemlessly for you.
>
> Another ASP.NET specific server application logic would need to be written
> to relay the message sent from person A to person B and vice versa. This
> app would also tell your listener app who is logged in, etc.
>
> That's how it would be done in .NET.
>
> Good luck!
>
> --
> Peter O'Reilly
>
>

I think I need to clarify this a little more.

What I'm asking is if anyone has written/purchased an instant messaging
system for use on a website. ie: a web client that communicates and stores
messages on a server so that another client can retrieve them and send new
messages in turn...


so the architecture would be something like


client > server > client


Like a chat-room, but instead of being open to x number of chatters - there
can only be 2. Is that clearer?


Chris



<chris@yahoo.com> wrote in message
news:%23Txy19sUDHA.3312@tk2msftngp13.phx.gbl...

> Has anyone built a web-based instant messaging system - or bought one?
> Looking for anyone who has implemented/purchased one already for
> advice/pointers/ any suggestions?
>
>
> Cheers
>
> Chris
>
>