sharing sessions among JSP and ASP.NET

We have applications written by JSP/Servlet and ASP.NET. All our future
development would be based on ASP.NET.


We wants to develop a single user interface so that users would not be aware
that some of the modules they are using are implement by JSP or ASP.NET
(e.g. no need to login both JSP and ASP.NET applications)? Are there any
suggestions to share the session in formation among JSP and ASP.NET, or some
single-sign on solution.

Thanks.

qube3

Don't really no about that.
But i know ASP and ASP.NET don't share sessions.
PAtrick


"qube3" wrote:

> We have applications written by JSP/Servlet and ASP.NET. All our future
> development would be based on ASP.NET.
>
>
> We wants to develop a single user interface so that users would not be aware
> that some of the modules they are using are implement by JSP or ASP.NET
> (e.g. no need to login both JSP and ASP.NET applications)? Are there any
> suggestions to share the session in formation among JSP and ASP.NET, or some
> single-sign on solution.
>
> Thanks.
>
>
>

=?Utf-8?B?UGF0cmljay5PLklnZQ==?=

Hi Mr.Patrick,
I would like to inform you about session sharing. ASP and ASP.NET can share
the same session. In our company we use ASP and ASP.NET applications which
share the same session.

If you wish you can find the article about that on MSDN Library following
the link below

http://msdn.microsoft.com/library/de...rttoaspnet.asp

But i really don't have any idea about session sharing between JSP and
ASP.NET. Using SQL Server as the state server can be a solution. The idea of
sharing session between ASP and ASP.NET which is discussed in the article is
based on this principle.

--
No Sign


"Patrick.O.Ige" wrote:

> Don't really no about that.
> But i know ASP and ASP.NET don't share sessions.
> PAtrick
>
>
> "qube3" wrote:
>
> > We have applications written by JSP/Servlet and ASP.NET. All our future
> > development would be based on ASP.NET.
> >
> >
> > We wants to develop a single user interface so that users would not be aware
> > that some of the modules they are using are implement by JSP or ASP.NET
> > (e.g. no need to login both JSP and ASP.NET applications)? Are there any
> > suggestions to share the session in formation among JSP and ASP.NET, or some
> > single-sign on solution.
> >
> > Thanks.
> >
> >
> >

=?Utf-8?B?YmFzdWxhc3o=?=

There is also an article about sessions on migration from JSP to ASP.NET on
the following link;

http://msdn.microsoft.com/library/en...Management.asp
--
No Sign


"Patrick.O.Ige" wrote:

> Don't really no about that.
> But i know ASP and ASP.NET don't share sessions.
> PAtrick
>
>
> "qube3" wrote:
>
> > We have applications written by JSP/Servlet and ASP.NET. All our future
> > development would be based on ASP.NET.
> >
> >
> > We wants to develop a single user interface so that users would not be aware
> > that some of the modules they are using are implement by JSP or ASP.NET
> > (e.g. no need to login both JSP and ASP.NET applications)? Are there any
> > suggestions to share the session in formation among JSP and ASP.NET, or some
> > single-sign on solution.
> >
> > Thanks.
> >
> >
> >

=?Utf-8?B?YmFzdWxhc3o=?=

million thanks!

"basulasz" <> ¦b¶l¥ó
news5A10A5C-D2EB-4686-AFB3- ¤¤¼¶¼g...
> There is also an article about sessions on migration from JSP to ASP.NET
on
> the following link;
>
>
http://msdn.microsoft.com/library/en...Management.asp
> --
> No Sign
>
>
> "Patrick.O.Ige" wrote:
>
> > Don't really no about that.
> > But i know ASP and ASP.NET don't share sessions.
> > PAtrick
> >
> >
> > "qube3" wrote:
> >
> > > We have applications written by JSP/Servlet and ASP.NET. All our
future
> > > development would be based on ASP.NET.
> > >
> > >
> > > We wants to develop a single user interface so that users would not be
aware
> > > that some of the modules they are using are implement by JSP or
ASP.NET
> > > (e.g. no need to login both JSP and ASP.NET applications)? Are there
any
> > > suggestions to share the session in formation among JSP and ASP.NET,
or some
> > > single-sign on solution.
> > >
> > > Thanks.
> > >
> > >
> > >

qube3