1. Config file

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
name: ht100x-kind
nodes:

Sofle Keyboard GitHub
Sofle build guide

Total price for 1 kit: X.XXX.XXX SEK

| Name | Quantity | Price | Link | Comments |

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

• 120 hp avklarad / 135 hp för de som skriver exjobbet i P4.
• Avklarad viktiga kurser som kretsar sig runt din frågeställning.
• Ta fram en frågeställning. (Vad vill du bli bättre på?)
  • Kom på en idé själv och presentera det till företag. Det kan vara bättre att komma på egen frågeställning åt företag än att de ska komma på en åt dig. Det kan resultera till att du får ett samtal av de.
  • Bestäm frågeställningen utifrån vad du är intrsserad av.
• Ta kontakt med möjliga handledare.
• Anmäl till Peter Sillén ([email protected]) att du vill bli tillkallad till möte om exjobb i augusti.

• Common time requirements of 8 hours is to high, difficult to asses that everyone can.
• GSC, should not have to be reported to the peers but instead give informall feedback. (Good, Bad, and Better)
• Canvas page is not updated.
• Iteration 1, should be more focused on [research, get to know the group, more theoretical focus, roll and understanding what the documents that we are going to work on] and an other thing is that the Examinator should provide the first iteration plan which both gives the student a good base line to start from and how it could work.
• Before the course start, share the information on how the course is laid out, what is obligatory to attend and what needs to be done. This will help studenet plan their hours before hand.
• Improvement on usage of technical resourses.
• Canvas hand-in during the week-ends.

• Two different access levels:
  1. user EXEC level. Basic monitoring commands.
  2. privileged EXEC level. Access all router commands, password protected to only allow only authorized user, configure or manage routers. There are five commands:
  3. Global configuration mode.
  4. Interface configuration mode.

3. Subinterface configuration mode.

This documentation is for helping student with completing the task 3. There will be minimal of code and just the structure of how I developed the application.

1. Our frist task is to set up the server where we are listening to a specific port.

$ java HTTPAsk 8888

1. In your constructor create global variables for your shutdown, timeout, and limit. Make sure you have default value when you aren't sending any values.
2. Copy in your solution from task1, method: askServer.
3. Add limiter variable, this variable will be used to limit the range of message fetching from server. It should have a default value of your buffer-size. It will get the default value when either the limit is higher than your buffer-size or when limit is at 0 (your default value from constructor). If the limit is less the your buffer-size and not zero then make it assigned the value from global variable.
4. Add timeout value in socket. READ HERE
5. Add counter variable, which it can either be the limit (global variable) or a [default value](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/net/Socket.html#getReceiveBufferSi