Search Results

Search found 76226 results on 3050 pages for 'google api java client'.

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

Page 651/3050 | < Previous Page | 647 648 649 650 651 652 653 654 655 656 657 658  | Next Page >

  • Appropriate design / technologies to handle dynamic string formatting?

    - by Mark W
    recently I was tasked with implementing a way of adding support for versioning of hardware packet specifications to one of our libraries. First a bit of information about the project. We have a hardware library which has classes for each of the various commands we support sending to our hardware. These hardware modules are essentially just lights with a few buttons, and a 2 or 4 digit display. The packets typically follow the format {SOH}AADD{ETX}, where AA is our sentinel action code, and DD is the device ID. These packet specs are different from one command to the next obviously, and the different firmware versions we have support different specifications. For example, on version 1 an action code of 14 may have a spec of {SOH}AADDTEXT{ETX} which would be AA = 14 literal, DD = device ID, TEXT = literal text to display on the device. Then we come out with a revision with adds an extended byte(s) onto the end of the packet like this {SOH}AADDTEXTE{ETX}. Assume the TEXT field is fixed width for this example. We have now added a new field onto the end which could be used to say specify the color or flash rate of the text/buttons. Currently this java library only supports one version of the commands, the latest. In our hardware library we would have a class for this command, say a DisplayTextArgs.java. That class would have fields for the device ID, the text, and the extended byte. The command class would expose a method which generates the string ("{SOH}AADDTEXTE{ETX}") using the value from the class. In practice we would create the Args class as needed, populate the fields, call the method to get our packet string, then ship that down across the CAN. Some of our other commands specification can vary for the same command, on the same version, depending on some runtime state. For example, another command for version 1 may be {SOH}AA{ETX}, where this action code clears all of the modules behind a specific controller device of their text. We may overload this packet to have option fields with multiple meanings like {SOH}AAOC{ETX} where OC is literal text, which tells the controller to only clear text on a specific module type, and to leave the others alone, or the spec could also have an option format of {SOH}AADD{ETX} to clear the text off a a specific device. Currently, in the method which generates the packet string, we would evaluate fields on the args class to determine which spec we will be using when formatting the packet. For this example, it would be along the lines of: if m_DeviceID != null then use {SOH}AADD{ETX} else if m_ClearOCs == true then use {SOH}AAOC{EXT} else use {SOH}AA{ETX} I had considered using XML, or a database to store String.format format strings, which were linked to firmware version numbers in some table. We would load them up at startup, and pass in the version number of the hardwares firmware we are currently using (I can query the devices for their firmware version, but the version is not included in all packets as part of the spec). This breaks down pretty quickly because of the dynamic nature of how we select which version of the command to use. I then considered using a rule engine to possibly build out expressions which could be interpreted at runtume, to evaluate the args class's state, and from that select the appropriate format string to use, but my brief look at rule engines for java scared me away with its complexity. While it seems like it might be a viable solution, it seems overly complex. So this is why I am here. I wouldn't say design is my strongest skill, and im having trouble figuring out the best way to approach this problem. I probably wont be able to radically change the args classes, but if the trade off was good enough, I may be able to convince my boss that the change is appropriate. What I would like from the community is some feedback on some best practices / design methodologies / API or other resources which I could use to accomplish: Logic to determine which set of commands to use for a given firmware version Of those command, which version of each command to use (based on the args classes state) Keep the rules logic decoupled from the application so as to avoid needing releases for every firmware version Be simple enough so I don't need weeks of study and trial and error to implement effectively.

    Read the article

  • IBM lancera sa suite bureautique Cloud LotusLive Symphony pour contrer Google, Microsoft et Oracle

    IBM lancera sa suite bureautique Cloud LotusLive Symphony pour contrer Google, Microsoft et Oracle Jusqu'ici, IBM proposait plusieurs outils professionnels en mode hébergé (partage de fichiers, messagerie instantanée et vidéo-conférence, mails, etc.) avec LotusLive. Mais le numéro 2 mondial du logiciel ne proposait pas de suite bureautique. Un problème qui allait devenir stratégique puisque le numéro 1, Microsoft, a lancé l'été dernier ses Office Web Apps, et le numéro 3, Oracle, son Cloud Office en fin d'année. IBM a donc ann...

    Read the article

  • How to Make My Website Come Up First in Google Fast

    Many people believe wrongly that it is very difficult to get a website to come up on the first page of Google. In fact, provided you follow a very simple step by step method it is really very easy even to get a brand new website up to the top of the results. Follow along and I will show you how to get your site to number one.

    Read the article

  • How to Get a Website Indexed by Google in 24 Hours

    Many people have a hard time getting new websites in the search engines. For most people, getting a new site indexed is extremely important, since they may have to rely on the free search engine traffic in the beginning to get their site going. In this article I will go over some strategies that I use to get my new websites indexed by Google within a day or so.

    Read the article

  • 7 Ways to Get Ranked in Google Within 24 Hours

    In order for a website to receive more targeted visits, it needs to get indexed by major search engines like Google. But if you don't know the right strategy, it can take weeks before search engine spiders crawl into your pages. Listed below are proven techniques on how you can get indexed in less than 24 hours.

    Read the article

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

< Previous Page | 647 648 649 650 651 652 653 654 655 656 657 658  | Next Page >