Carl wrote: > Keep us in the loop. Whatever happens, I smell a useful article here > on whatever tips/tricks/pitfalls you discover. You are dealing with > various third parties and various protocols in a time sensitive > application, so whatever you find will be interesting, even if you > have to mock up the actual material (since you can't seem to talk > about specifics this is understandable) I think it would still be > interesting to read.
I don't know, thinking about this, it sounds like: a) build a bunch of observers b) gather data c) put data in email d) fire email 5) get coffee (hey, it's Friday, I'm allowed to change bulleting style). So who do you think is better at watching? I think the gem that was suggested earlier on may really be all he needs.. And a way to manage it all. I wonder, if you really want to shave off milliseconds, string manipulation is probably too high level for you, but I am guessing by now that you are dealing with human-readable data. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
