I want to see what is being sent from Splunk universal forwarder using their "cooked" format version 3. Does anybody know how this format is encoded?
This is what I am currently seeing:
"--splunk-cooked-mode-v3--\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000e4a2da812b43\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u00008089\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000#\u0000\u0000\u0000\u0001\u0000\u0000\u0000\u0013__s2s_capabilities\u0000\u0000\u0000\u0000\u0014ack=0;compression=0\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0005_raw\u0000"
That protocol is proprietary and unpublished.
Related
I have built a web application which provides simple text chatting. I have used the UCWA API provided by Microsoft to implement this Instant Messaging chat application.
My next step is to enable usage of smilies/emoticons in the chat application. I have gone though the ucwa documentation https://ucwa.lync.com/documentation
But i have not found a way to enable usage of smilies/emoticons.
My query is: Does UCWA API support usage of smilies/emoticons? If yes, how do we enable in our chat application. If No, how can we add smilies/emoticons into a web application?
Any sort of links or any clues would be really helpful.
Thanks in Advance.
Simple Answer
Most Smilies/Emoticons are a translation of a string of characters into a visible image.
Examples:
:) ==>
(bah) ==>
UCWA has no knowledge of the image assets nor would you want it tossing around image data when in most cases a textual representation would result in a smaller response message. There is no native support.
Smilies/Emoticons that appear in Lync Client are a result of the application translating the string into an image resource. If you were to send a :), Lync Client should translate it to a .
What can I do?
Translate local display of supported Smilies/Emoticons to their image counter parts. (Probably the easiest)
Support sending of Html messages and send the Smilie/Emoticon and hope the receiving participant can access the image resource defined in an tag. (Probably the worst idea)
Make use of Emoji since UCWA is able to send/receive UTF encoded messages. Consider extensive testing to make sure that deployed environments can correctly display the results!
I have used Trello.NET to integrate Trello into our own bugtracking application.
Our own application has an european date format (dd/MM/yyyy). the Trello API has an American format (MM/dd/yyyy). TrelloNet uses RestSharp to do the REST communication.
How can change the serialization output to MM/dd/yyyy?
Kind Regard,
Tom
This is a bug in Trello.NET which was fixed in version 0.5.2.
I have an app that relies on some key value pairs where the value could change at a point in the future due to 3rd party api. The app is only useful when connected to the internet by the way. If any values change I don't want issue a new version of the app - I would rather that these values were pulled from a webservice/static xml file on my server. I would only need to pull these if I encountered an error.
Is there a standard way to do this or should I just roll my own?
EDIT: I'm not so interested in a server side technology - I think a flat file will suffice. What I'm interested in is what format should the flat file should be and how to cache it into my application once I get an error.
try redis, high-performance key-value store. used by some of the big cloud players, like cloudfoundry. Have a look at http://redis.io/. Objective-c client is available at http://redis.io/clients.
I figured out the best way for my use scenario:
I setup a json file on S3 which required authentication. I then used AWS for Objective C to authenticate so I could access that file.
I decided that I only needed to update the local info when the applicationDidBecomeActive in the App Delegate. I then got the json async and on success I then checked a version number in the json and if outdated wrote the changes to NSUSerDefaults (which are then used through the app.) If there was an error getting the json file I just continued as I would already have the previous set of NSUserDefaults that would do the job until the user next made the app active.
This solution worked best for me as it's simple to maintain and should easily handle the load even if my app were popular.
Have you considered using iCloud? It has support for key value pairs. More info here: http://developer.apple.com/library/ios/#documentation/iphone/conceptual/iphoneosprogrammingguide/iCloud/iCloud.html
I have a GPS tracker that sends the following sms message when sent a *1234*x# sms.
UnArmed;Engine:off;Door:off;LAC:2728;CID:EE62;Signal Strength:17$GPRMC,150105.00,A,0637.99406,N,00320.91465,E,0.022,,181011,,,A*76
I am trying to do 2 things.
Decode the message so I can create a server for it.
Possibly identify the tracker model to see if it also has GPRS capabilities.
I "inherited" it from an existing health mission that tracks rural ambulances, and the documentation is non existent and also the supplier has closed shop.
Thanks in advance
It looks like everything after the $ is a standard NMEA sentence. Everything before the $ looks pretty straightforward.
Where do I start?
Is there some sort of API - or something I can get access to that allows me to format articles and send them to my kindle?
I would like to do this in Rails.
Edit: For further clarity, I guess my real question is, how does instapaper.com get articles from the web to my kindle? Can someone explain the technology behind that please and do they have access to the Kindle SDK?
Take a look at Calibre (http://calibre-ebook.com/), runs on Linux, Win and OS X. Python based, has a GUI and a command line, suitable for automation. You can do all kind of conversions to .mobi format as well as fetching news from website and packing it to .mobi, which can be then transferred via USB or sent to kindle email address. It's very simple to fetch & send articles automatically either on a server system with cron or leaving it running on desktop (with GUI) for non-technical users.
Calibre's command line tools are your best bet: http://calibre-ebook.com/user_manual/cli/ebook-convert.html is the call you would most likely be interested in.
I believe all Instapaper does is convert to .mobi format, and then send mail (with the .mobi file attached) to your specified Kindle email address (eg. foo#kindle.com).
If you're more interested in specifics, Marco (Instapaper's author) tends to be very forthcoming when people ask him technical questions. His Twitter account is #marcoarment.
Check out this ruby gem, it seems to do what you want:
https://github.com/29decibel/kindler