[apparatus-templi] Re: Next weeks meeting
- From: Jonathan Nelson <ciasaboark@xxxxxxxxx>
- To: Christopher Hagler <haglerchristopher@xxxxxxxxx>
- Date: Sat, 25 Jan 2014 15:01:49 -0500
ccing this to the mailing list so everyone gets a copy
The xbee adapter that I showed is only available from adafruit. There are some
other ones out there, but that one was the only one that did voltage regulation
and was breadboard compatible.
I was hoping to avoid a dependency on apache, since the original model only
responded to simple GET requests (i.e. GET driver_widget?driver=some_driver)
but that may be the easiest way to go if we want to add user authentication
later. If you want to take care of the php (or whatever language you choose)
code and the responding parts of Coordinator that would be great.
I haven’t found a way to bridge apache cgi to a java backend yet. We may have
to use one of the java servlet servers (tomcat or jetty).
--
Jonathan Nelson
On Saturday, January 25, 2014 at 12:54 PM, Christopher Hagler wrote:
> I forgot to mention, It is fairly easy to write common gateway scripts for
> Apache web server that can do exactly what we want. Instead of having to code
> a whole new web server, we can just write CGI scripts for Apache. We would
> have the security of Apache and be able to use post and get requests.
>
>
> On Sat, Jan 25, 2014 at 12:49 PM, Christopher Hagler
> <haglerchristopher@xxxxxxxxx (mailto:haglerchristopher@xxxxxxxxx)> wrote:
> > I would like to work on the core, and the Web server, anything to do with
> > the main system. I have ordered my arduino uno, xbee, USB cable, breadboard
> > kit with electrical components, and a soldering kit. It should be here
> > Tuesday. I was only able to get one of each because the seller on amazon
> > only had one xbee. I was also unable to find the xbee adapter kit on
> > amazon, so I don't have that either. I was hoping I could meet with you one
> > day after my arduino arrived, so I could get you to introduce me into
> > getting it working and programming it.
> >
> >
> > Sent from my Samsung Galaxy S®4
> >
> >
> > -------- Original message --------
> > From: Jonathan Nelson
> > Date:01/25/2014 12:04 PM (GMT-05:00)
> > To: Christopher Hagler ,Kimberly Riley ,Terrence Mikell
> > Subject: Next weeks meeting
> >
> > For next weeks meeting I’d like to take some time to break the project down
> > into tasks can be assigned to specific team members. We should be able to
> > break the project into four main chunks:
> >
> > 1. the coordinator core
> > driver loading/verification
> > message passing
> > binary
> > text
> > logging
> > 2. coordinator persistant storage:
> > build a database model
> > implement code in coordinator
> > 3. coordinator frontend support:
> > develop an API for the front ends to use
> > small web server that responds to GET requests
> > 4. Web frontend
> > html, php, and javascript code to use the fronted API
> >
> > This still leaves us with our own drivers and arduino sketches to write,
> > and does not include the documentation or some things listed in the
> > milestones. If anyone has a specific part that they want to work on just
> > let me know.
> >
> > I’ve also updated the github page so that commit digests are forwarded to
> > the mailing list after anyone pushes their code to the server.
> > --
> > Jonathan Nelson
>
Other related posts:
