• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

java/MIDI/JDBC architecture confusion

Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am trying to set up an app involving both a database using JDBC and mySQL, and communication through the client's MIDI ports. I basically want to be able to store MIDI sysex data in the database, display it for the user, and allow them to edit it and send it to their synthesizer. So my client is not really "thin", and I think I will have to use an applet for the MIDI part (presuming that will work--is that outside applet rules??). Problem is, this needs to run on mac, which doesn't have a v2 jvm yet, and I'd like tables to display the data. And I guess applets can't communicate directly with the DB, right??
It looks like the jdk 1.3 midi implementation doesn't include any sysex control--it just plays back standard midi files, right? I've downloaded the independent implementation "JMidi" for mac and PC, and I need to verify that it can work in an applet.... If not, then what?? Seems like this should be possible.
Any ideas, architecture-wise??
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!