Integration Requirements
Justin Karr
An important discussion that was tabled at Monday's community design
was what specific existing technologies and products ATHENA Tix should
integrate with. I would like to restart this discussion here.
This includes everything from protocols and techniques (must be able
to communicate via SOAP) to specific component software (must support
PostgreSQL and run in JBoss) to specific applications (must integrate
directly with Microsoft Dynamics/GP).
So, hit me. Lay it on. The more detail, both about what and why, the
better.
Out of the gate, I am going to suggest:
1. Servlet Container Support: Tomcat, Jetty and JBoss at the very
least with an aim at being as container-agnostic as possible.
2. SQL databases: MySQL, PostgreSQL, HSQL at the very least with an
aim at being as DB-agnostic as possible.
Justin
Stjepan Rajko
An important discussion that was tabled at Monday's community design
was what specific existing technologies and products ATHENA Tix should
integrate with. I would like to restart this discussion here.
Is there any documentation available on specific workflows that ATHENA Tix should support? It would help me in thinking of relevant technologies/products that it should integrate with.
Best,
Stjepan
Justin Karr
Stjepan et al.,
Shortly we will be posting the actual workflows and requirements that came out of Monday's design session. The hold-up is just that they are currently very analog - post-it poster pages which were hung on the walls around the room. We are digitizing them and getting them into a format suitable to put up on the site.
I'm optimistic we will have some of them up later on today.
Justin
Stjepan Rajko
I guess a couple of things that might be relevant are:
* support OpenID for user authentication (e.g., for the admins / members of the organization selling the tickets, as well ticket buyers if logging in is a part of their workflows)
* support OAuth to allow third-party apps (or components within the system) to perform requests on behalf of users.
Best,
Stjepan
Stjepan et al.,
Shortly we will be posting the actual workflows and requirements that came out of Monday's design session. The hold-up is just that they are currently very analog - post-it poster pages which were hung on the walls around the room. We are digitizing them and getting them into a format suitable to put up on the site.
I'm optimistic we will have some of them up later on today.
Justin
From: athena-ti...@googlegroups.com [mailto:athena-ti...@googlegroups.com] On Behalf Of Stjepan Rajko
Sent: Wednesday, December 09, 2009 11:43 AM
To: athena-ti...@googlegroups.com
Subject: [athena-tix-planning] Re: Integration Requirements
On Wed, Dec 9, 2009 at 9:28 AM, Justin Karr <justi...@fracturedatlas.org> wrote:
Justin Karr
messages about technical integrations should be posted there.
On Dec 9, 12:05 pm, Stjepan Rajko <stjepan.ra...@gmail.com> wrote:
> Thanks Justin!
>
> I guess a couple of things that might be relevant are:
>
> * support OpenID for user authentication (e.g., for the admins / members of
> the organization selling the tickets, as well ticket buyers if logging in is
> a part of their workflows)
> * support OAuth to allow third-party apps (or components within the system)
> to perform requests on behalf of users.
>
> Best,
>
> Stjepan
>
> On Wed, Dec 9, 2009 at 9:48 AM, Justin Karr
>
>
> > Stjepan et al.,
>
> > Shortly we will be posting the actual workflows and requirements that came
> > out of Monday's design session. The hold-up is just that they are currently
> > very analog - post-it poster pages which were hung on the walls around the
> > room. We are digitizing them and getting them into a format suitable to put
> > up on the site.
>
> > I'm optimistic we will have some of them up later on today.
>
> > Justin
>
> > athena-ti...@googlegroups.com] *On Behalf Of *Stjepan Rajko
> > *Sent:* Wednesday, December 09, 2009 11:43 AM
> > *To:* athena-ti...@googlegroups.com
> > *Subject:* [athena-tix-planning] Re: Integration Requirements