I need to ask questions about LEACH
If anyone can help please let me know.
"I'm using LEACH script that generated by mannaaim."
Q1: I need to know how is the cluster membership in LEACH?
In other words, How can I know which nodes are belonging in each cluster?
Q2: How can I steer/control the traffic in LEACH in order to develop the routing protocol.
PS: If you have any documentation about LEACH generated by mannasim that can help.
Related
The objective is to create a custom action that returns the RTT from any requested domain. In other words I want to tell the assistant to Ping whatever domain and provide me with the RTT or respond that the server isn't reachable. Whereas I'm not ignorant or unable to research and apply results, I've not seen any similar project or a web-hook that would be easily applied. I've got some IFTTT experience and have created Glitch projects that have provided me with additional utility for the assistant. Honestly ''created'' is an overstatement, implementation was just a little step above script-kiddie abilities. The result was that the assistant now provides me with more functionality to control my media center on a Firestick than Amazon's skill does.
So, my assumption is that this is a pretty low level skill. I have no interest in this being anything other than a personal action. That said, I can handle invocation and all the other overhead necessary for human interface...etc but would surely appreciate assistance, references to similar projects or a helpful overview of what one thinks is the best method to accomplish the task.
If you are reading this and wondering why I posted here, please provide me with a more appropriate or topical forum location.
TIA
I have been trying out kubernetes on GCP to build microservices for a while and it has been amazing so far.
Although i am a bit confused on what would probably be the best approach, should i
create (gcloud container clusters create "[cluster-name]" ...) one container-cluster per service?
create one container-cluster for multiple services? or
do both of those above depending on my situation?
all of the examples i have managed to find has only covered #2, but my hunch is kind of telling me that i should do #1, and my hunch is also kind of telling me that i have probably missed some basic understanding around containers, i have been trying to find answers without any luck, i guess i just can't figure out the right search keyword, i am hoping that i could find some answer here.
I suspect the answer is "it depends" (Option 3)
How isolated do you need each application to be? How much redundancy (tolerance of VM failure) do you need? How many developers will have access to the Kubernetes cluster? How much traffic do the apps generate?
If in doubt I recommend running all your apps on a single cluster. Simpler to manage and the overhead in providing highly available infrastructure is then shared. You'll also have greater levels of VM utilization, which perhaps might result in reduced hosting costs. The latter is a subjective observation, some apps have very little or occasional traffic resulting in very bored servers :-)
I have this very old online game client (MMO) that has gone offline, and I want to make a server to this client.
I saw a lot of this kind of servers like World of Warcraft private servers.
I think that is not illegal do this to this with this client because the company is long gone, and I will not distribute...
So, how do I start reversing this client to make a server? Do I need to capture the database requests and build a database based on the requests? I think that probably this go way further. Can you help me?
Can you give some examples?
Thanks everyone.
There was a good post on reverse engineering subreddit about this a little bit ago.
There are a few links with peoples experiences. Effectively you will play the game of trying to make your client happy by "answering" packets with your server if you dont have packet captures to go after. I would first identify packet parsing logic within the client. A good way of doing this is tracing recv() calls backwards and generally you will find a giant function (or a few functions) that contain a switch statement. Hopefully you'll find some useful strings, else you're just going to be playing the "keep the client happy" guessing game.
Can anybody explain me what exactly Resource manager do. Thanks in advance.
Basically, you can use this for creating internationalized applications.
It is a single point of access that allows you to retrieve internationalized data from your resource bundles.
Here are some useful official links on the matter:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/resources/ResourceManager.html
http://livedocs.adobe.com/flex/3/html/help.html?content=l10n_6.html
And some unofficial:
http://sujitreddyg.wordpress.com/2008/01/22/localizing-flex-applications
http://www.visible-form.com/blog/flex-localization-with-resource-bundles/
Cheers
I've been tasked with using a 'Geo Cookie' to identify where in the world users are accessing the site from, and to redirect them to a site configured for their region.
I understand what a cookie is in the context of the web, but I'm not sure about a geo cookie, partly because I've never heard of one before.
Could somebody please tell me if this a real thing, or if it could be a term that was made up by people who didn't know the proper name for what they're really talking about? (this happens quite regularly, it seems). Is there any way for me to identify where the user is located?
I'd never heard of the term before, and doing a little googling confirmed my suspicion that this is not a common term in usage.
My thoughts, reading off of the first search result from that query, is that you're being asked to implement a cookie that stores the users region. This can be done with a normal cookie, and you can give it the name "GEO" - viola! A Geo Cookie.
If I were you, I'd go back to the stakeholder and find out what this requirement means.
For determining where a user is located (without asking the directly) you can use the ip of the user, and a geo-location service. See Know a good IP address Geolocation Service for more info on that.
A geo cookie is just a cookie which you store the geo data in.
This allows you to:
Avoid having to hit the geo/ip database with each request
Allow users to override the location (e.g. I know it looks like I'm in Spain, and as it happens, I am (yay holidays), but I want data for England, that is where I live, and that is where I want my results localised to).